Resource allocation and user multiplexing capacity enhancements for interlace based physical uplink control channel formats in new radio (nr)-unlicensed

ABSTRACT

Systems and methods are described for a resource allocation and user multiplexing capacity enhancements for interlace based physical uplink control channel (PUCCH) formats in new radio (NR) using unlicensed spectrum (NR-U). The systems and methods can include at least generating, by the UE, an uplink signal according to a physical uplink control channel (PUCCH) format and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace, and transmitting, by the UE, the uplink signal over a PUCCH that utilizes unlicensed spectrum in a new radio wireless network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/826,947, filed Mar. 29, 2019, which is hereby incorporated by reference in its entirety.

FIELD

Various embodiments generally may relate to the field of wireless communications.

SUMMARY

Embodiments are directed to a method of operating a user equipment (UE) for resource allocation and user multiplexing capacity enhancements for interlace based physical uplink control channel (PUCCH) formats in new radio (NR) using unlicensed spectrum (NR-U). The method can include at least generating, by the UE, an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace, and transmitting, by the UE, the uplink signal over a PUCCH that utilizes unlicensed spectrum in a new radio wireless network.

The method can further include determining, by the UE, a value of “n” based on an uplink control information (UCI) payload size, choosing, by the UE, a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.

The method can further include receiving, by the UE, one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.

The method can further include generating based on determining, by the UE, a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.

The method can further include configuring, by the UE, a starting interlace and a number of interlaces as a PUCCH resource allocation for PUCCH format 2 in a frequency domain.

The method can further include generating based on determining, by the UE, a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).

The method can further include the Δ_(PRB) being restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.

Embodiments are directed to a non-transitory computer readable medium having instructions stored thereon that, when executed by a user equipment (UE), cause the UE to perform operations including at least generating an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain of a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace, and transmitting the uplink signal over a PUCCH that utilizes unlicensed spectrum in a new radio wireless network.

The operations can further include determining a value of “n” based on an uplink control information (UCI) payload size, and choosing a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.

The operations can further include receiving one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.

The operations can further include generating based on determining a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.

The operations can further include generating based on configuring a starting interlace and a number of interlaces as a PUCCH resource allocation for PUCCH format 2 in a frequency domain.

The operations can further include generating based on determining a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).

The operations can further include Δ_(PRB) being restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.

Embodiments are directed to a user equipment (UE). The UE can include at least a processor circuitry configured to generate an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace, and radio front end circuitry, coupled to the processor circuitry, configured to transmit the uplink signal on a PUCCH that utilizes unlicensed spectrum of new radio wireless network.

The processor circuitry can be further be configured to determine a value of “n” based on an uplink control information (UCI) payload size, and choose a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.

The processor circuitry can further be configured to receive one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.

The processor circuitry can further be configured to determine a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.

The processor circuitry can further be configured to determine a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).

The Δ_(PRB) can be restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates an example mapping of n PRBs on one or more interlaces for SCS=30 KHz and B=20 MHz, in accordance with some embodiments.

FIG. 2 illustrates an example front loaded DMRS for PUCCH format 3 with TDM'd DMRS and UCI patterns, in accordance with some embodiments.

FIG. 3 illustrates an example of length-4 OCC applied to PUCCH format 2 with different OCC index pattern on each PRB, in accordance with some embodiments.

FIG. 4 illustrates an example of pre-DFT blockwise spread OCC of length-120 applied on PRB based interlace structure of PUCCH format 3 (10 PRBs/interlace) to multiplex 2 UEs on odd and even combs, in accordance with some embodiments.

FIG. 5 depicts an architecture of a system of a network in accordance with some embodiments.

FIG. 6 depicts an architecture of a system including a first core network in accordance with some embodiments.

FIG. 7 depicts an architecture of a system including a second core network in accordance with some embodiments.

FIG. 8 depicts an example of infrastructure equipment in accordance with various embodiments.

FIG. 9 depicts example components of a computer platform in accordance with various embodiments.

FIG. 10 depicts example components of baseband circuitry and radio frequency circuitry in accordance with various embodiments.

FIG. 11 is an illustration of various protocol functions that may be used for various protocol stacks in accordance with various embodiments.

FIG. 12 depicts a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perforin any one or more of the methodologies discussed herein.

FIG. 13 depicts an example procedure for practicing the various embodiments discussed herein, including resource allocation and user multiplexing capacity enhancements for interlace based PUCCH formats in MR-U.

The features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number.

DETAILED DESCRIPTION Discussion of Embodiments

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B).

Mobile communication has advanced remarkably in the past two decades: emerging from early voice systems and transforming into today's highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) is going to provide ubiquitous connectivity and access to information, as well as ability to share data, around the globe. NR is expected to be a unified framework that will target to meet versatile and sometimes, conflicting performance criteria and provide services to vastly heterogeneous application domains ranging from Enhanced Mobile Broadband (eMBB) to massive Machine-Type Communications (mMTC) and Ultra-Reliable Low-Latency Communications (URLLC), to name a few. In general, NR will evolve based on third generation partnership project (3GPP) long term evolution (LTE)-Advanced technology with additional enhanced radio access technologies (RATs) to enable seamless and faster wireless connectivity solutions.

One major enhancement for LTE in Rel-13 has been to enable the operation of cellular networks in the unlicensed spectrum, via Licensed-Assisted-Access (LAA). Ever since, exploiting the access of unlicensed spectrum is considered by 3GPP as one of the promising solutions to cope with the increasing growth of wireless data traffic. One of the important considerations for LTE to operate in unlicensed spectrum is to ensure fair co-existence with incumbent systems like wireless local area networks (WLANs), which has been the primary focus of LAA standardization effort since Rel. 13.

Following the trend of LTE enhancements, study on NR based access to unlicensed spectrum (NR-unlicensed) has started in 3GPP Rel-15. Within the scope of this work item, one of the primary objectives is to identify additional functionalities that are needed for a physical (PHY) layer design of NR to operate in unlicensed spectrum. In particular, it is desirable to minimize the design efforts by identifying the essential enhancements needed for Rel-15 NR design to enable unlicensed operation, while avoiding unnecessary divergence from Rel-15 NR licensed framework. Coexistence methods already defined for LTE-based LAA context should be assumed as the baseline for the operation of NR-unlicensed systems, while enhancements over these existing methods are not precluded. NR-based operation in unlicensed spectrum should not impact deployed Wi-Fi services (data, video and voice services) more than an additional Wi-Fi network on the same carrier.

Regulatory requirements must be mandatorily met by networks and systems operating in unlicensed spectrum. One of such regulatory restrictions imposed on physical channels/signals operating in unlicensed spectrum is related to the bandwidth occupied by these channels/signals, referred to as Occupied Channel Bandwidth (OCB). According to European Telecommunications Standards Institute (ETSI) harmonised standard for 5 GHz, limits on OCB are as follows: The Occupied Channel Bandwidth shall be between 80% and 100% of the Nominal Channel Bandwidth. In case of smart antenna systems (devices with multiple transmit chains) each of the transmit chains shall meet this requirement. The Occupied Channel Bandwidth might change with time/payload. During a Channel Occupancy Time (COT), equipment may operate temporarily with an Occupied Channel Bandwidth of less than 80% of its Nominal Channel Bandwidth with a minimum of 2 MHz.

In addition to restrictions on OCB, there are important regulatory rules on power usage by networks and systems operating in unlicensed spectrum, as follows: Regulations on the maximum power spectral density are typically stated with a resolution bandwidth of 1 MHz. The ETSI specification requires a maximum Power Spectral Density (PSD) of 10 dBm/MHz for 5150-5350 MHz, while Federal Communications Commission (FCC) has a maximum PSD of 11 dBm/MHz for 5150-5350 MHz. Additionally, regulations require 10 KHz resolution for testing the 1 MHz PSD constraint and, thus, the maximum PSD constraint should be met in any occupied 1 MHz bandwidth.

In addition, the regulations impose a band specific total maximum transmission power in terms of EIRP, e.g., ESTI has EIRP limit of 23 dBm for 5150-5350 MHz.

The regulatory limitations imposed in terms of OCB and PSD guided the design choices for the uplink channels of legacy LTE-unlicensed system and it will not be any different for NR-unlicensed system as well. Though it is desirable to avoid unnecessary divergence from Rel-15 NR framework as much as possible while designing uplink physical signals/channels for NR-unlicensed spectrum, the regulatory constraints will necessitate enhancements of NR physical signals/channels to certain extents in order to meet the essential requirements of unlicensed spectrum usage.

The legacy PUCCH design is based on different PUCCH formats (in particular, NR-PUCCH formats 2 and 3) used in NR licensed spectrum. Legacy NR-licensed PUCCH design is not suitable for NR-unlicensed spectrum, since unlicensed spectrum utilization is restricted by regulatory limitations, especially in terms of OCB and PSD, which may not be fulfilled by existing NR-PUCCH formats designed for licensed spectrum.

In the above context, the present disclosure provides enhancements of NR physical uplink control channel (PUCCH) formats 2 and 3 to support user multiplexing and meet the regulatory requirements in unlicensed spectrum by enhancing resource allocation in frequency domain. In particular, the embodiments discussed herein include enhancements of NR PUCCH formats to enable user multiplexing in NR-unlicensed (NR-U); and details of signaling aspect related to PUCCH transmission for NR-U. The enhanced NR PUCCH formats 2/3 of the embodiments herein enable user multiplexing over unlicensed spectrum. Additionally, the embodiments herein provide necessary signaling mechanisms for the transmission of uplink control information (UCI) over PUCCH using unlicensed spectrum.

The baseline structures of NR-PUCCH formats 2 and 3 have been agreed as follows:

NR PUCCH Format 2

Demodulation reference signal (DMRS) and UCI are multiplexed in frequency division multiplexing (FDM) manner on different frequency sub-carriers in a symbol and can span over 1-2 symbols in time, whereas 1-16 PRBs frequency.

-   -   DMRS locations within a PRB are at RE locations 1, 4, 7 and 10,         with RE indexing starting from 0 (e.g., within each PRB, 12         sub-carriers are indexed 0-11).     -   Pseudo noise (PN) sequence is used for DMRS sequence.     -   UCI bits are QPSK modulated after encoding and scrambling to         form UCI symbols.     -   The number of PRBs is determined by the total number of UCI bits         and the configured maximum coding rate.     -   PRBs are allocated in a contiguous manner.

Format 2 typically carries greater than 2 bits of UCI payload, which can be channel state information (CSI) reports with or without HARQ-ACK bit(s) and/or SR bit.

For 2-symbol NR PUCCH format 2.

-   -   Encoded UCI bits are scrambled and distributed across the         symbols.     -   DM-RS density and pattern of 1-symbol PUCCH format 2 is used for         each symbol of 2-symbol PUCCH format 2.     -   Frequency hopping is supported between two symbols.

NR PUCCH Format 3

Demodulation reference signal (DMRS) and UCI are multiplexed in time division multiplexing (TDM) manner on different discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) symbols and can span over 4-14 symbols within a slot in time, whereas up to 16 PRBs across frequency.

-   -   The number and location of DMRS symbol(s) within a slot depends         on the length of PUCCH as well as whether frequency hopping is         enabled or disabled.     -   DMRS symbol(s) are formed by a length-12 sequence in frequency         domain when PUCCH format 3 spreads across 1 PRB in frequency         domain. For more than one PRBs, DMRS sequences used for         DFT-s-OFDM physical uplink shared channel (PUSCH) is used.     -   UCI bits are encoded, scrambled, QPSK modulated and         DFT-pre-coded to form UCI symbols.     -   The number of PRBs is determined by the total number of UCI bits         and the configured maximum coding rate.     -   Number of PRBs can be factored into 2^(a)*3^(b)*5^(c) where a,         b, c are integers.     -   PRBs are allocated in a contiguous manner across frequency.

Format 3 can typically carries greater than 2 bits of UCI payload, which can be CSI reports with or without HARQ-ACK bit(s) and/or SR bit.

Intra-slot frequency hopping can be enabled with at most one hop and the hopping boundary is located near the middle of N-symbol PUCCH format 3.

-   -   Number of symbols in the 1^(st) and 2^(nd) hops are └N/2┘ and         ┌N/2┐ respectively.

During the Rel-16 work item on “NR based access to unlicensed spectrum”, it has been agreed to support interlace based PUCCH transmission to meet regulatory requirements and one UE will be assigned to at least one full interlace for transmission of uplink data (e.g., via physical uplink shared channel (PUSCH)) or uplink control information (e.g., via PUCCH). One of the potential ways to support interlace based PUCCH transmission is to enhance the existing multi-PRB PUCCH, viz. NR PUCCH formats 2 and 3 to support interlace based frequency mapping. However, neither NR PUCCH format 2 nor NR PUCCH format 3 allows user multiplexing on the same time-frequency resource and hence have limited UE multiplexing capacity within a slot. In this context, potential enhancements of NR-PUCCH 2/3 to enhance UE multiplexing capacity and time/frequency domain resource allocation are described in details as follows.

Enhancements of time/frequency domain structure for PUCCH format 2

In one embodiment, PUCCH format 2 may be configured by higher layer signaling, for example, by RRC configuration, with n number of PRBs which are mapped non-contiguously (e.g., in interlaced manner) across frequency domain on each OFDM symbol so as to meet the OCB criteria. Here, n can be determined by the total number of uplink control information (UCI) bits and the configured maximum coding rate, and n≤┌{OCB/(N_(RB) ^(SC)*SCS)}┐. Here, OCB is the minimum occupied channel bandwidth requirement mandated by regulation, SCS is the subcarrier spacing and Na is the number of sub-carriers within one resource block, which is the resource allocation unit for block-interlace based transmission. As one example, N_(RB) ^(SC)=12 for PRB based interlace.

In one option, n may be an integer multiple of number of PRBs per interlace, for example, n=x_(int)*y_(PRB) ^(int), where x_(int) is the number of interlaces assigned to PUCCH format 2 transmission (x_(int) ^(max)≥x_(int)≥1), x_(int) ^(max) is the maximum number of interlaces available within the scheduled transmission bandwidth B having N_(RB) number of usable PRBs (i.e. x_(int) ^(max)=└N_(RB)/y_(PRB) ^(int)┘), and y_(PRB) ^(int) is the number of PRBs per interlace (as one example, y_(PRB) ^(int)=10).

In this case, a UE would always use an integer number of full interlaces, depending in the determined value of n based on UCI payload size, and UE may choose a code rate less than the configured maximum code rate in order to determine the appropriate value of n that is divisible by y_(PRB) ^(int). Frequency domain resources provided to the UE via higher layer signaling may include interlace indices, where each interlace with certain index number i (i=0, 1, . . . , x_(int) ^(max)−1) may be pre-defined in the specification in terms of starting PRB, inter-PRB separation and number-of-PRB s per interlace. A bitmap based approach may be used to indicate which interlaces to be used (e.g., a binary string of x_(int) ^(max) bits may be used, where “1”s indicate the interlace indices to be used for PUCCH transmission. For example, for x_(int) ^(max)=5, a bitmap “10010” indicates that interlace indices ‘0’ and ‘3’ are to be used.) Alternatively, higher layer signaling may only indicate the interlace index of the first interlace and the subsequent (x_(int)−1) interlace indices to be used may be derived implicitly by some pre-defined rules. In this case, the index of the first interlace to be used can be indicated by either bitmap or by k bits, where k=┌log₂ (x_(int) ^(max))┐.

In another option, certain combinations of interlaces to be used for frequency allocation of PUCCH format 2 (and 3) can be predefined. In one example, assuming maximally 2 full interlaces are used for PUCCH format 2, and totally 5 interlaces are defined, then the combinations can be defined as 0, 1, 2, 3, 4 for one interlace case, {0 2}, {1, 3}, {0, 1} {1, 2}, {2,3} {3,4} for two full interlace case. Note that this option may help reduce the signaling overhead.

In another option, the starting interlace and the number of interlaces can be configured as PUCCH resource allocation for PUCCH format 2 (and 3) in frequency domain. The bitwidth may depend on the maximum number of interlaces regardless of the numerology configured for the UL bandwidth part (BWP) or depend on the number of interlaces within 20 MHz in accordance with the configured numerology for UL BWP.

In another option, n may not be an integer multiple of number of PRBs per interlace, e.g., n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), where Δ_(PRB)<y_(PRB) ^(int). In this case, there may be certain restrictions applied on the permissible values of Δ_(PRB) depending on the allowed resource allocation unit granularity beyond an integer number of full interlace allocations. These excess Δ_(PRB) PRBs may be mapped on the same interlace index (e.g., consecutive or non-consecutive Δ_(PRB) PRBs corresponding to a single interlace index i) or on more than one interlaces. Frequency domain resources provided to the UE via higher layer signaling may include interlace indices for full interlace allocations as mentioned in the above embodiment and an additional one bit signaling that indicates if a non-zero Δ_(PRB) is allowed or not. Depending on the value of this bit, UE may either implicitly derive the locations of Δ_(PRB) PRBs on one or more interlaces based on some pre-defined rule or the locations of Δ_(PRB) excess PRBs may be explicitly signaled to the UE by higher layer signaling, or a combination thereof.

As one example, when all these Δ_(PRB) PRBs are assigned to one interlace, the interlace index might be either signaled to the UE separately by a bitmap or “k” bits, or may be jointly encoded and signaled to the UE along with the interlace indices for full interlace assignment, or may be implicitly derivable. On another example, when these Δ_(PRB) PRBs are assigned on different interlaces, either only the interlace indices are explicitly indicated and UE may implicitly derive the PRB locations within each of these interlaces based on some pre-defined rule, or both the interlace indices and PRB locations within each interlace are jointly encoded and signaled to the UE, or UE may implicitly derive both the interlaces indices and the locations of Δ_(PRB) PRBs on these interlaces using some pre-defined rules, or a combination thereof.

In one alternative, Δ_(PRB) may be restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1. As one example, for y_(PRB) ^(int)=10, Δ_(PRB)={2,5}. In that case, UE may choose a code rate less than the configured maximum code rate in order to determine the appropriate value of n such that, in case it is not divisible by y_(PRB) ^(int), the excess Δ_(PRB) PRBs would be a factor of y_(PRB) ^(int). In this case, in addition to full interlaces, resource allocation units can be in terms of partial interlace, which contains y_(PRB) ^(partial) number of PRBs, where y_(PRB) ^(partial) is a factor of y_(PRB) ^(int). Such partial interlaces may be predefined in the specification and UE may either be explicitly indicated by higher layer signaling all the indices of full and partial interlaces to be used, or UE may implicitly derive these full and partial interlace indices based on the first interlace index provided by higher layer signaling, using some pre-defined rules, or a combination thereof.

In another alternative, Δ_(PRB) may not be restricted to be a factor of y_(PRB) ^(int), e.g., UE can determine any value of n depending on its payload size and maximum configured code rate, which may result in Δ_(PRB)>0, not necessarily a factor of y_(PRB) ^(int). In this case, the frequency allocation of these excess Δ_(PRB) PRBs may either be explicitly indicated to the UE by higher layer signaling, or may be implicitly derived based on some pre-defined rules (which may be a function of the allocated full interlace indices) or a combination thereof.

FIG. 1 illustrates an example of n PRBs allocated to one or more interlaces. The example shown here is for 30 KHz SCS for which N_(RB)=51 for B=20 MHz. There are in total 5 interlaces (102, 104, 106, 108, and 110), with each interlace having 10 PRBs. In 102, the PRBs corresponding to interlace index 0 is shown. For n=10, all the PRBs corresponding to a full interlace (interlace 0) is assigned. For n=15, Δ_(PRB)=5 can be assigned to a partial interlace (constituting 5 consecutive PRBs on one interlace) on interlace index 1 (e.g., the very next interlace index which can be implicitly derived based on pre-defined rule or can be indicated by higher layer) in 104 and on interlace index 2 (e.g., on one interlace with index that is a fixed UE-specific or higher layer signaled offset away from the 1^(st) interlace) in 108 respectively. In another option, the PRBs within the 2nd interlace may not be consecutive and a fixed offset (e.g., 10 PRBs in between two consecutive mapped PRBs) may be applied which may be either be implicitly derived by some pre-defined rule or may be provided explicitly by higher layer signaling, as shown in 106 and 110 on interlace indices 1 and 2 respectively.

In another embodiment, for N-symbol NR PUCCH format 2, where N>1 (e.g., N=2), similar enhancements as mentioned in the above embodiments can be applied, where the same frequency domain resource allocation on one symbol can be repeated across N symbols of PUCCH format 2.

In another embodiment, for N-symbol NR PUCCH format 2/3, where N>1, frequency hopping can be made always disabled, since frequency diversity can already be achieved by interlace based resource allocation.

Enhancements of Time/Frequency Domain Structure for PUCCH Format 3

In one embodiment, PUCCH format 3 may be configured by higher layer signaling (for example, by RRC configuration), with n number of PRBs which are mapped non-contiguously (e.g., in interlaced manner) across frequency domain on each UCI symbol, so as to meet the OCB criteria. Here, n can be determined by the total number of UCI bits and the configured maximum coding rate, and n≤┌{OCB/(12*SCS)}┐, n=2^(a)*3^(b)*5^(c). Here, OCB is the minimum occupied channel bandwidth requirement mandated by regulation, SCS is the subcarrier spacing and N_(RB) ^(SC) is the number of sub-carriers within one resource block, which is the resource allocation unit for block-interlace based transmission. As one example, N_(RB) ^(SC)=12 for PRB based interlace. For PUCCH format 3 based on DFT-s-OFDM, N_(RB) ^(SC)=2^(a)*3^(b)*5^(c), where {a, b, c} are integers. All the embodiments mentioned above regarding frequency domain resource enhancements are applicable to PUCCH format 3 as well, with the additional restriction that n=2^(a)*3^(b)*5^(c) for DFT-s-OFDM based PUCCH format 3. Alternatively, if CP-OFDM is used for interlace based enhanced PUCCH format 3, the restriction on n can be relaxed.

In another embodiment, for N-symbol NR PUCCH format 3 (4≤N≤14), frequency hopping can be made always disabled, since frequency diversity can already be achieved by interlace based resource allocation.

In one embodiment, time domain structure of enhanced PUCCH format 3, e.g., the TDM pattern of UCI and DMRS symbols can be modified from NR PUCCH format 3 so as to facilitate early/fast detection of transmission at gNB side, since in unlicensed band, the channel access is based on listen-before-talk (LBT) and hence UE's transmission is subject to clear channel assessment (CCA) success. In one option, only the first DMRS symbol for PUCCH format 3 are shifted to the first symbol. For instance, for PUCCH format 3 with 6 symbol duration, symbol {1,4} are allocated for DMRS. In this case, new DMRS position is symbol {0,4}.

In another option, all the DMRS symbols are shifted left accordingly so that the first symbol is allocated for DMRS symbol. For instance, for PUCCH format 3 with 6 symbol duration, symbol {1,4} are allocated for DMRS. In this case, new DMRS position is symbol {0,3}.

For example, in the first option, front loaded DMRS structure can be considered for enhanced PUCCH format 3, as shown by FIG. 2, which illustrates an example front loaded DMRS for PUCCH format 3 with TDM'd DMRS and UCI patterns.

Enhancements of UE Multiplexing Capacity for PUCCH Format 2

In one embodiment, length-n_(UE) orthogonal cover codes (OCCs) can be applied on n_(RS) DMRS and n_(UCI) UCI symbols FDM'd on each PRB of interlace based PUCCH format 2, respectively and n_(UE) users can be code domain multiplexed on the same time—frequency resources using OCCs on DMRS and UCI symbols on each PRB, where n_(UE)≤min{n_(RS), n_(UCI)} and n_(UE) is a common factor of n_(RS) and n_(UCI).

As one example, for n=10 PRBs assigned to interlace based PUCCH format 2, where 8 UCI symbols and 4 DMRS symbols are FDM'd on each PRB, length-4 OCCs can be applied on DMRS and UCI symbols, mapped on each PRB, to enable up to 4 UEs to be multiplexed on the same time/frequency resource.

In one option, the OCCs applied on UCI symbols may be the same codes as that applied on DMRS symbols. For example, DFT based OCCs may be applied on both UCI and DMRS symbols, when there is no restriction on n_(UE). On the other hand, if n_(UE) can be expressed as power of 2 (e.g., 2^(x), x being an integer), then Walsh-code based OCC can be used for both DMRS and UCI symbols.

In another option, different OCCs may be applied on DMRS and UCI symbols. For example, DMRS OCC may be based on Walsh-code whereas UCI-OCC may be based on DFT-code and vice versa.

In another embodiment, in addition to frequency domain OCC on each PRB, time domain OCC can be applied across OFDM symbols if N>1. Either the same OCC applied across frequency domain can be applied across time domain, or different time domain OCC may be used.

In one embodiment, on each PRB, the OCC indices applied to multiplexed UEs may be different in order to randomize the OCC pattern over all PRBs and reduce resulting peak-to-average power ratio (PAPR).

In one example, for length-x OCC applied on DMRS and UCI symbols on each PRB, the OCC indices used for UE1, . . . , UE(x) on 1^(st) PRB may be {C₀, C₁, . . . , C_(x−1)} respectively, whereas on i^(th) PRB, the OCC indices used may be {C_((i−1)modx), C_((imodx)), . . . , C_((i+x−2)modx)} respectively.

In another example, the OCC indices used by one UE on 1^(st) PRB may be incremented by a UE-specific offset value on every subsequent PRBs on one or more interlace(s) assigned to the UE, which may be provided by higher layer signaling.

In another example, the OCC randomization patterns used for DMRS symbols and UCI symbols may be same or different. In one example, the OCC randomization may be defined as a function of one or more of the following parameters: physical or virtual cell ID, symbol/slot/frame index, etc. Note that the OCC randomization may be applied for the PUCCH format 3 enhancement when OCC is applied for the transmission of UCI, which can help reduce PAPR.

FIG. 3 illustrates an example of frequency domain OCC applied on 1-symbol PUCCH format 2 mapped on 10 PRBs within one interlace. 4 UEs are multiplexed on one interlace, which mean on each PRB data and RS symbols are repeatedly mapped 4 times and OCC code of length-4 is applied on repeated UCI and DMRS symbols for each UE, with different OCC indices. For example, for length-4 DFT based OCC, the OCCs applied to UCI symbols of UE1, UE2, UE3 and UE4 on the 1^(st) PRB shown in the figure by 302 would be [1 −1 1 −1]; [1 j −1 −j]; [1 −j −1 j]; {[1 1 1 1]}, e.g., {C2; C3; C1; C0}. Similarly, in the 2^(nd) PRB shown in the figure by 304, the OCC indices are shifted by a pre-defined offset and the OCC indices applied to UE1 through 4 on this PRB are {[1 1 1 1]; [1 −j −1 j]; [1 −1 1 −1]; [1 j −1 −j]}, e.g., {C0; C1; C2; C3}. In this example, the same length-4 OCC is applied to DMRS symbols on each PRB as well. In the figure, the label Dij denotes the j-th UCI symbol for i-th UE and Rij denotes the j-th DMRS symbol for i-th UE.

In another embodiment, instead of OCC pattern randomization, symbol level scrambling may be used on UCI symbols after applying OCC to minimize PAPR. In this case, the same OCC index or different OCC index may be used for a UE on all PRBs. Note that QPSK modulation is employed after the pseudo noise (PN) sequence generation. Further, the symbol level scrambling may be cell specific or UE specific. In particular, the initialization of scrambling sequence may be defined as one or more following parameters: physical or virtual cell ID, symbol/slot/frame index, UE ID (e.g., C-RNTI), etc.

In one example, the PN sequence can be initialized as C_(init)=n_(ID). In case when n_(ID)=n_(ID) ^(cell), same scrambling sequence can be generated, which is mainly for PAPR reduction.

Note that the symbol level scrambling may be applied for the PUCCH format 3 enhancement when OCC is applied for the transmission of UCI, which can help reduce PAPR.

In another embodiment, different UEs are multiplexed on interlace based PUCCH format 2 either in frequency division multiplexing manner (e.g., on different interlaces) or time division multiplexing manner (e.g., on different OFDM symbols within a slot) only and code domain multiplexing is not allowed.

In another embodiment, the OCC applied for the transmission of DMRS may be implicitly derived from the OCC for the transmission of UCI symbols for PUCCH format 2. In one example, same OCC index is applied for the transmission of DMRS and UCI symbols.

Enhancements of UE Multiplexing Capacity for PUCCH Format 3

In one embodiment, CDM based UE multiplexing can be enabled on enhanced interlace based PUCCH format 3 by extending the pre-DFT block-wise OCC spreading (applied on single PRB in Rel-15 NR PUCCH format 4) to all PRBs on one or more interlaces assigned to enhanced PUCCH format 3. By extending pre-DFT OCC block-wise to all PRBs, UCI symbols of each multiplexed UEs are mapped on orthogonal combs and hence, irrespective of channel delay spread the orthogonality between transmissions of different UEs retains.

FIG. 4 illustrates an example of pre-DFT blockwise spread OCC applied on UCI symbols mapped on one interlace with 10 PRB s/interlace and spreading factor=2. For UE0, a block of data {d₀, . . . , d₅₉} is repeated in two blocks on which, OCC [1 1 . . . 1 |1 1 . . . 1] is applied before DFT operation. The resulting DFT coded symbols are mapped on even combs (e.g., on subcarriers with indices 0, 2, 4, . . . , 118) on 10 PRBs or 120 REs. For UE1, a block of data {s₀, . . . , s₅₉} is repeated in two block on which, OCC [1 1 . . . 1 |−1 −1 . . . −1] is applied before DFT operation. The resulting DFT coded symbols are mapped on odd combs e.g., subcarriers with indices {1, 3, 5, . . . , 119} on the same 10 PRBs or 120 REs of the interlace.

In another embodiment, on top of pre-DFT OCC, time domain OCC can be applied where the OCC may be the same as the pre-DFT OCC (before blockwise spreading) or different OCC.

In another embodiment, the cyclic shift for the transmission of DMRS may be configured as part of PUCCH resource for PUCCH format 3. In another option, the cyclic shift for the transmission of DMRS may be implicitly derived from the pre-DFT OCC index for the transmission of UCI symbols for PUCCH format 3. In particular, assuming the number of cyclic shifts for DMRS as N_(CS), and the number of pre-DFT OCC index as N_(OCC), then the cyclic shift index can be derived as

$I_{cs} = {\frac{N_{cs}}{N_{occ}} \cdot {I_{occ}.}}$

For instance, assuming 12 cyclic shifts for DMRS and 4 pre-DFT OCCs, the pre-DFT OCC index as {0,1,2,3}, then the corresponding cyclic shift index is {0,3,6,9}.

Systems and Implementations

FIG. 5 illustrates an example architecture of a system 500 of a network, in accordance with various embodiments. The following description is provided for an example system 500 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WLAN, WiMAX, etc.), or the like.

As shown by FIG. 5, the system 500 includes UE 501 a and UE 501 b (collectively referred to as “UEs 501” or “UE 501”). In this example, UEs 501 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and/or the like.

In some embodiments, any of the UEs 501 may be IoT UEs, which may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UEs 501 may be configured to connect, for example, communicatively couple, with an or RAN 510. In embodiments, the RAN 510 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to a RAN 510 that operates in an NR or 5G system 500, and the term “E-UTRAN” or the like may refer to a RAN 510 that operates in an LTE or 4G system 500. The UEs 501 utilize connections (or channels) 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).

In this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs 501 may directly exchange communication data via a ProSe interface 505. The ProSe interface 505 may alternatively be referred to as a SL interface 505 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 501 b is shown to be configured to access an AP 506 (also referred to as “WLAN node 506,” “WLAN 506,” “WLAN Termination 506,” “WT 506” or the like) via connection 507. The connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 501 b, RAN 510, and AP 506 may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE 501 b in RRC_CONNECTED being configured by a RAN node 511 a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 501 b using WLAN radio resources (e.g., connection 507) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 507. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN 510 can include one or more AN nodes or RAN nodes 511 a and 511 b (collectively referred to as “RAN nodes 511” or “RAN node 511”) that enable the connections 503 and 504. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNB s, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node 511 that operates in an NR or 5G system 500 (for example, a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node 511 that operates in an LTE or 4G system 500 (e.g., an eNB). According to various embodiments, the RAN nodes 511 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes 511 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 511; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 511; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 511. This virtualized framework allows the freed-up processor cores of the RAN nodes 511 to perform other virtualized applications. In some implementations, an individual RAN node 511 may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by FIG. 5). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs (see, e.g., FIG. 8), and the gNB-CU may be operated by a server that is located in the RAN 510 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 511 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 501, and are connected to a 5GC (e.g., CN 720 of FIG. 7) via an NG interface (discussed infra).

In V2X scenarios one or more of the RAN nodes 511 may be or act as RSUs. The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 501 (vUEs 501). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.

Any of the RAN nodes 511 can terminate the air interface protocol and can be the first point of contact for the UEs 501. In some embodiments, any of the RAN nodes 511 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In embodiments, the UEs 501 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 511 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 to the UEs 501, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

According to various embodiments, the UEs 501 and the RAN nodes 511 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 501 and the RAN nodes 511 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs 501 and the RAN nodes 511 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs 501 RAN nodes 511, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 501, AP 506, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE 501 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 501. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 501 b within a cell) may be performed at any of the RAN nodes 511 based on channel quality information fed back from any of the UEs 501. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501.

The PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.

The RAN nodes 511 may be configured to communicate with one another via interface 512. In embodiments where the system 500 is an LTE system (e.g., when CN 520 is an EPC 620 as in FIG. 6), the interface 512 may be an X2 interface 512. The X2 interface may be defined between two or more RAN nodes 511 (e.g., two or more eNBs and the like) that connect to EPC 520, and/or between two eNBs connecting to EPC 520. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 501 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 501; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system 500 is a 5G or NR system (e.g., when CN 520 is an 5GC 720 as in FIG. 7), the interface 512 may be an Xn interface 512. The Xn interface is defined between two or more RAN nodes 511 (e.g., two or more gNBs and the like) that connect to 5GC 520, between a RAN node 511 (e.g., a gNB) connecting to 5GC 520 and an eNB, and/or between two eNBs connecting to 5GC 520. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 501 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 511. The mobility support may include context transfer from an old (source) serving RAN node 511 to new (target) serving RAN node 511; and control of user plane tunnels between old (source) serving RAN node 511 to new (target) serving RAN node 511. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN 510 is shown to be communicatively coupled to a core network—in this embodiment, core network (CN) 520. The CN 520 may comprise a plurality of network elements 522, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 501) who are connected to the CN 520 via the RAN 510. The components of the CN 520 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 520 may be referred to as a network slice, and a logical instantiation of a portion of the CN 520 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 530 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 via the EPC 520.

In embodiments, the CN 520 may be a 5GC (referred to as “5GC 520” or the like), and the RAN 510 may be connected with the CN 520 via an NG interface 513. In embodiments, the NG interface 513 may be split into two parts, an NG user plane (NG-U) interface 514, which carries traffic data between the RAN nodes 511 and a UPF, and the S1 control plane (NG-C) interface 515, which is a signaling interface between the RAN nodes 511 and AMFs. Embodiments where the CN 520 is a 5GC 520 are discussed in more detail with regard to FIG. 7.

In embodiments, the CN 520 may be a 5G CN (referred to as “5GC 520” or the like), while in other embodiments, the CN 520 may be an EPC). Where CN 520 is an EPC (referred to as “EPC 520” or the like), the RAN 510 may be connected with the CN 520 via an S1 interface 513. In embodiments, the S1 interface 513 may be split into two parts, an S1 user plane (S1-U) interface 514, which carries traffic data between the RAN nodes 511 and the S-GW, and the S1-MME interface 515, which is a signaling interface between the RAN nodes 511 and MMEs.

FIG. 6 illustrates an example architecture of a system 600 including a first CN 620, in accordance with various embodiments. In this example, system 600 may implement the LTE standard wherein the CN 620 is an EPC 620 that corresponds with CN 520 of FIG. 5. Additionally, the UE 601 may be the same or similar as the UEs 501 of FIG. 5, and the E-UTRAN 610 may be a RAN that is the same or similar to the RAN 510 of FIG. 5, and which may include RAN nodes 511 discussed previously. The CN 620 may comprise MMEs 621, an S-GW 622, a P-GW 623, a HSS 624, and a SGSN 625.

The MMEs 621 may be similar in function to the control plane of legacy SGSN, and may implement MM functions to keep track of the current location of a UE 601. The MMEs 621 may perform various MM procedures to manage mobility aspects in access such as gateway selection and tracking area list management. MM (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, etc. that are used to maintain knowledge about a present location of the UE 601, provide user identity confidentiality, and/or perform other like services to users/subscribers. Each UE 601 and the MME 621 may include an MM or EMM sublayer, and an MM context may be established in the UE 601 and the MME 621 when an attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE 601. The MMEs 621 may be coupled with the HSS 624 via an Sha reference point, coupled with the SGSN 625 via an S3 reference point, and coupled with the S-GW 622 via an S11 reference point.

The SGSN 625 may be a node that serves the UE 601 by tracking the location of an individual UE 601 and performing security functions. In addition, the SGSN 625 may perform Inter-EPC node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MMEs 621; handling of UE 601 time zone functions as specified by the MMEs 621; and MME selection for handovers to E-UTRAN 3GPP access network. The S3 reference point between the MMEs 621 and the SGSN 625 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states.

The HSS 624 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC 620 may comprise one or several HSSs 624, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 624 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 624 and the MMES 621 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC 620 between HSS 624 and the MMEs 621.

The S-GW 622 may terminate the S1 interface 513 (“S1-U” in FIG. 6) toward the RAN 610, and routes data packets between the RAN 610 and the EPC 620. In addition, the S-GW 622 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The S11 reference point between the S-GW 622 and the MMES 621 may provide a control plane between the MMES 621 and the S-GW 622. The S-GW 622 may be coupled with the P-GW 623 via an S5 reference point.

The P-GW 623 may terminate an SGi interface toward a PDN 630. The P-GW 623 may route data packets between the EPC 620 and external networks such as a network including the application server 530 (alternatively referred to as an “AF”) via an IP interface 525 (see e.g., FIG. 5). In embodiments, the P-GW 623 may be communicatively coupled to an application server (application server 530 of FIG. 5 or PDN 630 in FIG. 6) via an IP communications interface 525 (see, e.g., FIG. 5). The S5 reference point between the P-GW 623 and the S-GW 622 may provide user plane tunneling and tunnel management between the P-GW 623 and the S-GW 622. The S5 reference point may also be used for S-GW 622 relocation due to UE 601 mobility and if the S-GW 622 needs to connect to a non-collocated P-GW 623 for the required PDN connectivity. The P-GW 623 may further include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW 623 and the packet data network (PDN) 630 may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The P-GW 623 may be coupled with a PCRF 626 via a Gx reference point.

PCRF 626 is the policy and charging control element of the EPC 620. In a non-roaming scenario, there may be a single PCRF 626 in the Home Public Land Mobile Network (HPLMN) associated with a UE 601's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE 601's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 626 may be communicatively coupled to the application server 630 via the P-GW 623. The application server 630 may signal the PCRF 626 to indicate a new service flow and select the appropriate QoS and charging parameters. The PCRF 626 may provision this rule into a PCEF (not shown) with the appropriate TFT and QCI, which commences the QoS and charging as specified by the application server 630. The Gx reference point between the PCRF 626 and the P-GW 623 may allow for the transfer of QoS policy and charging rules from the PCRF 626 to PCEF in the P-GW 623. An Rx reference point may reside between the PDN 630 (or “AF 630”) and the PCRF 626.

FIG. 7 illustrates an architecture of a system 700 including a second CN 720 in accordance with various embodiments. The system 700 is shown to include a UE 701, which may be the same or similar to the UEs 501 and UE 601 discussed previously; a (R)AN 710, which may be the same or similar to the RAN 510 and RAN 610 discussed previously, and which may include RAN nodes 511 discussed previously; and a DN 703, which may be, for example, operator services, Internet access or 3rd party services; and a 5GC 720. The 5GC 720 may include an AUSF 722; an AMF 721; a SMF 724; a NEF 723; a PCF 726; a NRF 725; a UDM 727; an AF 728; a UPF 702; and a NSSF 729.

The UPF 702 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 703, and a branching point to support multi-homed PDU session. The UPF 702 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 702 may include an uplink classifier to support routing traffic flows to a data network. The DN 703 may represent various network operator services, Internet access, or third party services. DN 703 may include, or be similar to, application server 530 discussed previously. The UPF 702 may interact with the SMF 724 via an N4 reference point between the SMF 724 and the UPF 702.

The AUSF 722 may store data for authentication of UE 701 and handle authentication-related functionality. The AUSF 722 may facilitate a common authentication framework for various access types. The AUSF 722 may communicate with the AMF 721 via an N12 reference point between the AMF 721 and the AUSF 722; and may communicate with the UDM 727 via an N13 reference point between the UDM 727 and the AUSF 722. Additionally, the AUSF 722 may exhibit an Nausf service-based interface.

The AMF 721 may be responsible for registration management (e.g., for registering UE 701, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 721 may be a termination point for the an N11 reference point between the AMF 721 and the SMF 724. The AMF 721 may provide transport for SM messages between the UE 701 and the SMF 724, and act as a transparent proxy for routing SM messages. AMF 721 may also provide transport for SMS messages between UE 701 and an SMSF (not shown by FIG. 7). AMF 721 may act as SEAF, which may include interaction with the AUSF 722 and the UE 701, receipt of an intermediate key that was established as a result of the UE 701 authentication process. Where USIM based authentication is used, the AMF 721 may retrieve the security material from the AUSF 722. AMF 721 may also include a SCM function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF 721 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the (R)AN 710 and the AMF 721; and the AMF 721 may be a termination point of NAS (N1) signalling, and perform NAS ciphering and integrity protection.

AMF 721 may also support NAS signalling with a UE 701 over an N3 IWF interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 710 and the AMF 721 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 710 and the UPF 702 for the user plane. As such, the AMF 721 may handle N2 signalling from the SMF 724 and the AMF 721 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS signalling between the UE 701 and AMF 721 via an N1 reference point between the UE 701 and the AMF 721, and relay uplink and downlink user-plane packets between the UE 701 and UPF 702. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 701. The AMF 721 may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs 721 and an N17 reference point between the AMF 721 and a 5G-EIR (not shown by FIG. 7).

The UE 701 may need to register with the AMF 721 in order to receive network services. RM is used to register or deregister the UE 701 with the network (e.g., AMF 721), and establish a UE context in the network (e.g., AMF 721). The UE 701 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 701 is not registered with the network, and the UE context in AMF 721 holds no valid location or routing information for the UE 701 so the UE 701 is not reachable by the AMF 721. In the RM-REGISTERED state, the UE 701 is registered with the network, and the UE context in AMF 721 may hold a valid location or routing information for the UE 701 so the UE 701 is reachable by the AMF 721. In the RM-REGISTERED state, the UE 701 may perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 701 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF 721 may store one or more RM contexts for the UE 701, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF 721 may also store a 5GC MM context that may be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF 721 may store a CE mode B Restriction parameter of the UE 701 in an associated MM context or RM context. The AMF 721 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

CM may be used to establish and release a signaling connection between the UE 701 and the AMF 721 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 701 and the CN 720, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 701 between the AN (e.g., RAN 710) and the AMF 721. The UE 701 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 701 is operating in the CM-IDLE state/mode, the UE 701 may have no NAS signaling connection established with the AMF 721 over the N1 interface, and there may be (R)AN 710 signaling connection (e.g., N2 and/or N3 connections) for the UE 701. When the UE 701 is operating in the CM-CONNECTED state/mode, the UE 701 may have an established NAS signaling connection with the AMF 721 over the N1 interface, and there may be a (R)AN 710 signaling connection (e.g., N2 and/or N3 connections) for the UE 701. Establishment of an N2 connection between the (R)AN 710 and the AMF 721 may cause the UE 701 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 701 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN 710 and the AMF 721 is released.

The SMF 724 may be responsible for SM (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 701 and a data network (DN) 703 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 701 request, modified upon UE 701 and 5GC 720 request, and released upon UE 701 and 5GC 720 request using NAS SM signaling exchanged over the N1 reference point between the UE 701 and the SMF 724. Upon request from an application server, the 5GC 720 may trigger a specific application in the UE 701. In response to receipt of the trigger message, the UE 701 may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE 701. The identified application(s) in the UE 701 may establish a PDU session to a specific DNN. The SMF 724 may check whether the UE 701 requests are compliant with user subscription information associated with the UE 701. In this regard, the SMF 724 may retrieve and/or request to receive update notifications on SMF 724 level subscription data from the UDM 727.

The SMF 724 may include the following roaming functionality: handling local enforcement to apply QoS SLAB (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signalling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs 724 may be included in the system 700, which may be between another SMF 724 in a visited network and the SMF 724 in the home network in roaming scenarios. Additionally, the SMF 724 may exhibit the Nsmf service-based interface.

The NEF 723 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF 728), edge computing or fog computing systems, etc. In such embodiments, the NEF 723 may authenticate, authorize, and/or throttle the AFs. NEF 723 may also translate information exchanged with the AF 728 and information exchanged with internal network functions. For example, the NEF 723 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 723 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 723 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 723 to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF 723 may exhibit an Nnef service-based interface.

The NRF 725 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 725 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 725 may exhibit the Nnrf service-based interface.

The PCF 726 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour. The PCF 726 may also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM 727. The PCF 726 may communicate with the AMF 721 via an N15 reference point between the PCF 726 and the AMF 721, which may include a PCF 726 in a visited network and the AMF 721 in case of roaming scenarios. The PCF 726 may communicate with the AF 728 via an N5 reference point between the PCF 726 and the AF 728; and with the SMF 724 via an N7 reference point between the PCF 726 and the SMF 724. The system 700 and/or CN 720 may also include an N24 reference point between the PCF 726 (in the home network) and a PCF 726 in a visited network. Additionally, the PCF 726 may exhibit an Npcf service-based interface.

The UDM 727 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 701. For example, subscription data may be communicated between the UDM 727 and the AMF 721 via an N8 reference point between the UDM 727 and the AMF. The UDM 727 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 7). The UDR may store subscription data and policy data for the UDM 727 and the PCF 726, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 701) for the NEF 723. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 727, PCF 726, and NEF 723 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. The UDR may interact with the SMF 724 via an N10 reference point between the UDM 727 and the SMF 724. UDM 727 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 727 may exhibit the Nudm service-based interface.

The AF 728 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC 720 and AF 728 to provide information to each other via NEF 723, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE 701 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 702 close to the UE 701 and execute traffic steering from the UPF 702 to DN 703 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 728. In this way, the AF 728 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 728 is considered to be a trusted entity, the network operator may permit AF 728 to interact directly with relevant NFs. Additionally, the AF 728 may exhibit an Naf service-based interface.

The NSSF 729 may select a set of network slice instances serving the UE 701. The NSSF 729 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 729 may also determine the AMF set to be used to serve the UE 701, or a list of candidate AMF(s) 721 based on a suitable configuration and possibly by querying the NRF 725. The selection of a set of network slice instances for the UE 701 may be triggered by the AMF 721 with which the UE 701 is registered by interacting with the NSSF 729, which may lead to a change of AMF 721. The NSSF 729 may interact with the AMF 721 via an N22 reference point between AMF 721 and NSSF 729; and may communicate with another NSSF 729 in a visited network via an N31 reference point (not shown by FIG. 7). Additionally, the NSSF 729 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 720 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 701 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 721 and UDM 727 for a notification procedure that the UE 701 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 727 when UE 701 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 7, such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and the like. The Data Storage system may include a SDSF, an UDSF, and/or the like. Any NF may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 7). Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Additionally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 7). The 5G-EIR may be an NF that checks the status of PEI for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there may be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 7 for clarity. In one example, the CN 720 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME 621) and the AMF 721 in order to enable interworking between CN 720 and CN 620. Other example interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

FIG. 8 illustrates an example of infrastructure equipment 800 in accordance with various embodiments. The infrastructure equipment 800 (or “system 800”) may be implemented as a base station, radio head, RAN node such as the RAN nodes 511 and/or AP 506 shown and described previously, application server(s) 530, and/or any other element/device discussed herein. In other examples, the system 800 could be implemented in or by a UE.

The system 800 includes application circuitry 805, baseband circuitry 810, one or more radio front end modules (RFEMs) 815, memory circuitry 820, power management integrated circuitry (PMIC) 825, power tee circuitry 830, network controller circuitry 835, network interface connector 840, satellite positioning circuitry 845, and user interface 850. In some embodiments, the device 800 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.

Application circuitry 805 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I²C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors (or cores) of the application circuitry 805 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 800. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 805 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuitry 805 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein. As examples, the processor(s) of application circuitry 805 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior P-class processors; and/or the like. In some embodiments, the system 800 may not utilize application circuitry 805, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 805 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. As examples, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of application circuitry 805 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 805 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.

The baseband circuitry 810 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 810 are discussed infra with regard to FIG. 10.

User interface circuitry 850 may include one or more user interfaces designed to enable user interaction with the system 800 or peripheral component interfaces designed to enable peripheral component interaction with the system 800. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.

The radio front end modules (RFEMs) 815 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 1011 of FIG. 10 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 815, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 820 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®. Memory circuitry 820 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.

The PMIC 825 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry 830 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 800 using a single cable.

The network controller circuitry 835 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment 800 via network interface connector 840 using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry 835 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 835 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry 845 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry 845 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 845 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 845 may also be part of, or interact with, the baseband circuitry 810 and/or RFEMs 815 to communicate with the nodes and components of the positioning network. The positioning circuitry 845 may also provide position data and/or time data to the application circuitry 805, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes 511, etc.), or the like.

The components shown by FIG. 8 may communicate with one another using interface circuitry, which may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus/IX may be a proprietary bus, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I²C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 9 illustrates an example of a platform 900 (or “device 900”) in accordance with various embodiments. In embodiments, the computer platform 900 may be suitable for use as UEs 501, 601, 701, application servers 530, and/or any other element/device discussed herein. The platform 900 may include any combinations of the components shown in the example. The components of platform 900 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 900, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 9 is intended to show a high level view of components of the computer platform 900. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

Application circuitry 905 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I²C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 905 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 900. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 805 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry 805 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.

As examples, the processor(s) of application circuitry 905 may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, Calif. The processors of the application circuitry 905 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry 905 may be a part of a system on a chip (SoC) in which the application circuitry 905 and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

Additionally or alternatively, application circuitry 905 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 905 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 905 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.

The baseband circuitry 910 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 910 are discussed infra with regard to FIG. 10.

The RFEMs 915 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 1011 of FIG. 10 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 915, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 920 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 920 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 920 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 920 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry 920 may be on-die memory or registers associated with the application circuitry 905. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 920 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform 900 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 923 may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 900. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform 900 may also include interface circuitry (not shown) that is used to connect external devices with the platform 900. The external devices connected to the platform 900 via the interface circuitry include sensor circuitry 921 and electro-mechanical components (EMCs) 922, as well as removable memory devices coupled to removable memory circuitry 923.

The sensor circuitry 921 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUS) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs 922 include devices, modules, or subsystems whose purpose is to enable platform 900 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 922 may be configured to generate and send messages/signalling to other components of the platform 900 to indicate a current state of the EMCs 922. Examples of the EMCs 922 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform 900 is configured to operate one or more EMCs 922 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform 900 with positioning circuitry 945. The positioning circuitry 945 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry 945 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 945 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 945 may also be part of, or interact with, the baseband circuitry 810 and/or RFEMs 915 to communicate with the nodes and components of the positioning network. The positioning circuitry 945 may also provide position data and/or time data to the application circuitry 905, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect the platform 900 with Near-Field Communication (NFC) circuitry 940. NFC circuitry 940 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 940 and NFC-enabled devices external to the platform 900 (e.g., an “NFC touchpoint”). NFC circuitry 940 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 940 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 940, or initiate data transfer between the NFC circuitry 940 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 900.

The driver circuitry 946 may include software and hardware elements that operate to control particular devices that are embedded in the platform 900, attached to the platform 900, or otherwise communicatively coupled with the platform 900. The driver circuitry 946 may include individual drivers allowing other components of the platform 900 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 900. For example, driver circuitry 946 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 900, sensor drivers to obtain sensor readings of sensor circuitry 921 and control and allow access to sensor circuitry 921, EMC drivers to obtain actuator positions of the EMCs 922 and/or control and allow access to the EMCs 922, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 925 (also referred to as “power management circuitry 925”) may manage power provided to various components of the platform 900. In particular, with respect to the baseband circuitry 910, the PMIC 925 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 925 may often be included when the platform 900 is capable of being powered by a battery 930, for example, when the device is included in a UE 501, 601, 701.

In some embodiments, the PMIC 925 may control, or otherwise be part of, various power saving mechanisms of the platform 900. For example, if the platform 900 is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 900 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 900 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 900 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform 900 may not receive data in this state; in order to receive data, it must transition back to RRC Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery 930 may power the platform 900, although in some examples the platform 900 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 930 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 930 may be a typical lead-acid automotive battery.

In some implementations, the battery 930 may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 900 to track the state of charge (SoCh) of the battery 930. The BMS may be used to monitor other parameters of the battery 930 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 930. The BMS may communicate the information of the battery 930 to the application circuitry 905 or other components of the platform 900. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 905 to directly monitor the voltage of the battery 930 or the current flow from the battery 930. The battery parameters may be used to determine actions that the platform 900 may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 930. In some examples, the power block XS30 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 900. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 930, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 950 includes various input/output (I/O) devices present within, or connected to, the platform 900, and includes one or more user interfaces designed to enable user interaction with the platform 900 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 900. The user interface circuitry 950 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 900. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry 921 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform 900 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I²C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG. 10 illustrates example components of baseband circuitry 1010 and radio front end modules (RFEM) 1015 in accordance with various embodiments. The baseband circuitry 1010 corresponds to the baseband circuitry 810 and 910 of FIGS. 8 and 9, respectively. The RFEM 1015 corresponds to the RFEM 815 and 915 of FIGS. 8 and 9, respectively. As shown, the RFEMs 1015 may include Radio Frequency (RF) circuitry 1006, front-end module (FEM) circuitry 1008, antenna array 1011 coupled together at least as shown.

The baseband circuitry 1010 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry 1006. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1010 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1010 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry 1010 is configured to process baseband signals received from a receive signal path of the RF circuitry 1006 and to generate baseband signals for a transmit signal path of the RF circuitry 1006. The baseband circuitry 1010 is configured to interface with application circuitry 805/905 (see FIGS. 8 and 9) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1006. The baseband circuitry 1010 may handle various radio control functions.

The aforementioned circuitry and/or control logic of the baseband circuitry 1010 may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor 1004A, a 4G/LTE baseband processor 1004B, a 5G/NR baseband processor 1004C, or some other baseband processor(s) 1004D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors 1004A-D may be included in modules stored in the memory 1004G and executed via a Central Processing Unit (CPU) 1004E. In other embodiments, some or all of the functionality of baseband processors 1004A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory 1004G may store program code of a real-time OS (RTOS), which when executed by the CPU 1004E (or other baseband processor), is to cause the CPU 1004E (or other baseband processor) to manage resources of the baseband circuitry 1010, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry 1010 includes one or more audio digital signal processor(s) (DSP) 1004F. The audio DSP(s) 1004F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

In some embodiments, each of the processors 1004A-1004E include respective memory interfaces to send/receive data to/from the memory 1004G. The baseband circuitry 1010 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 1010; an application circuitry interface to send/receive data to/from the application circuitry 805/905 of FIGS. 8-10); an RF circuitry interface to send/receive data to/from RF circuitry 1006 of FIG. 10; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 925.

In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry 1010 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry 1010 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 1015).

Although not shown by FIG. 10, in some embodiments, the baseband circuitry 1010 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 1010 and/or RF circuitry 1006 are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 1010 and/or RF circuitry 1006 are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 1004G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry 1010 may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 1010 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuitry 1010 may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry 1010 and RF circuitry 1006 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry 1010 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 1006 (or multiple instances of RF circuitry 1006). In yet another example, some or all of the constituent components of the baseband circuitry 1010 and the application circuitry 805/905 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry 1010 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1010 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodiments in which the baseband circuitry 1010 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 1006 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1006 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1006 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1010. RF circuitry 1006 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1010 and provide RF output signals to the FEM circuitry 1008 for transmission.

In some embodiments, the receive signal path of the RF circuitry 1006 may include mixer circuitry 1006A, amplifier circuitry 1006B and filter circuitry 1006C. In some embodiments, the transmit signal path of the RF circuitry 1006 may include filter circuitry 1006C and mixer circuitry 1006A. RF circuitry 1006 may also include synthesizer circuitry 1006D for synthesizing a frequency for use by the mixer circuitry 1006A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1006A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006D. The amplifier circuitry 1006B may be configured to amplify the down-converted signals and the filter circuitry 1006C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1010 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1006A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1006A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006D to generate RF output signals for the FEM circuitry 1008. The baseband signals may be provided by the baseband circuitry 1010 and may be filtered by filter circuitry 1006C.

In some embodiments, the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1010 may include a digital baseband interface to communicate with the RF circuitry 1006.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1006D may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1006D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1006D may be configured to synthesize an output frequency for use by the mixer circuitry 1006A of the RF circuitry 1006 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1006D may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1010 or the application circuitry 805/905 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 805/905.

Synthesizer circuitry 1006D of the RF circuitry 1006 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1006D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1006 may include an IQ/polar converter.

FEM circuitry 1008 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 1011, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing. FEM circuitry 1008 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of antenna elements of antenna array 1011. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1006, solely in the FEM circuitry 1008, or in both the RF circuitry 1006 and the FEM circuitry 1008.

In some embodiments, the FEM circuitry 1008 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 1008 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 1008 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1006). The transmit signal path of the FEM circuitry 1008 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 1011.

The antenna array 1011 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry 1010 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 1011 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array 1011 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array 1011 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 1006 and/or FEM circuitry 1008 using metal transmission lines or the like.

Processors of the application circuitry 805/905 and processors of the baseband circuitry 1010 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1010, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 805/905 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.

FIG. 11 illustrates various protocol functions that may be implemented in a wireless communication device according to various embodiments. In particular, FIG. 11 includes an arrangement 1100 showing interconnections between various protocol layers/entities. The following description of FIG. 11 is provided for various protocol layers/entities that operate in conjunction with the 5G/NR system standards and LTE system standards, but some or all of the aspects of FIG. 11 may be applicable to other wireless communication network systems as well.

The protocol layers of arrangement 1100 may include one or more of PHY 1110, MAC 1120, RLC 1130, PDCP 1140, SDAP 1147, RRC 1155, and NAS layer 1157, in addition to other higher layer functions not illustrated. The protocol layers may include one or more service access points (e.g., items 1159, 1156, 1150, 1149, 1145, 1135, 1125, and 1115 in FIG. 11) that may provide communication between two or more protocol layers.

The PHY 1110 may transmit and receive physical layer signals 1105 that may be received from or transmitted to one or more other communication devices. The physical layer signals 1105 may comprise one or more physical channels, such as those discussed herein. The PHY 1110 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC 1155. The PHY 1110 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing. In embodiments, an instance of PHY 1110 may process requests from and provide indications to an instance of MAC 1120 via one or more PHY-SAP 1115. According to some embodiments, requests and indications communicated via PHY-SAP 1115 may comprise one or more transport channels.

Instance(s) of MAC 1120 may process requests from, and provide indications to, an instance of RLC 1130 via one or more MAC-SAPs 1125. These requests and indications communicated via the MAC-SAP 1125 may comprise one or more logical channels. The MAC 1120 may perform mapping between the logical channels and transport channels, multiplexing of MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 1110 via the transport channels, de-multiplexing MAC SDUs to one or more logical channels from TBs delivered from the PHY 1110 via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.

Instance(s) of RLC 1130 may process requests from and provide indications to an instance of PDCP 1140 via one or more radio link control service access points (RLC-SAP) 1135. These requests and indications communicated via RLC-SAP 1135 may comprise one or more RLC channels. The RLC 1130 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 1130 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC 1130 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 1140 may process requests from and provide indications to instance(s) of RRC 1155 and/or instance(s) of SDAP 1147 via one or more packet data convergence protocol service access points (PDCP-SAP) 1145. These requests and indications communicated via PDCP-SAP 1145 may comprise one or more radio bearers. The PDCP 1140 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 1147 may process requests from and provide indications to one or more higher layer protocol entities via one or more SDAP-SAP 1149. These requests and indications communicated via SDAP-SAP 1149 may comprise one or more QoS flows. The SDAP 1147 may map QoS flows to DRBs, and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 1147 may be configured for an individual PDU session. In the UL direction, the NG-RAN 510 may control the mapping of QoS Flows to DRB(s) in two different ways, reflective mapping or explicit mapping. For reflective mapping, the SDAP 1147 of a UE 501 may monitor the QFIs of the DL packets for each DRB, and may apply the same mapping for packets flowing in the UL direction. For a DRB, the SDAP 1147 of the UE 501 may map the UL packets belonging to the QoS flows(s) corresponding to the QoS flow ID(s) and PDU session observed in the DL packets for that DRB. To enable reflective mapping, the NG-RAN 710 may mark DL packets over the Uu interface with a QoS flow ID. The explicit mapping may involve the RRC 1155 configuring the SDAP 1147 with an explicit QoS flow to DRB mapping rule, which may be stored and followed by the SDAP 1147. In embodiments, the SDAP 1147 may only be used in NR implementations and may not be used in LTE implementations.

The RRC 1155 may configure, via one or more management service access points

(M-SAP), aspects of one or more protocol layers, which may include one or more instances of PHY 1110, MAC 1120, RLC 1130, PDCP 1140 and SDAP 1147. In embodiments, an instance of RRC 1155 may process requests from and provide indications to one or more NAS entities 1157 via one or more RRC-SAPs 1156. The main services and functions of the RRC 1155 may include broadcast of system information (e.g., included in MIBs or SIBs related to the NAS), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE 501 and RAN 510 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. The MIBs and SIBs may comprise one or more IEs, which may each comprise individual data fields or data structures.

The NAS 1157 may form the highest stratum of the control plane between the UE 501 and the AMF 721. The NAS 1157 may support the mobility of the UEs 501 and the session management procedures to establish and maintain IP connectivity between the UE 501 and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities of arrangement 1100 may be implemented in UEs 501, RAN nodes 511, AMF 721 in NR implementations or MME 621 in LTE implementations, UPF 702 in NR implementations or S-GW 622 and P-GW 623 in LTE implementations, or the like to be used for control plane or user plane communications protocol stack between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 501, gNB 511, AMF 721, etc. may communicate with a respective peer protocol entity that may be implemented in or on another device using the services of respective lower layer protocol entities to perform such communication. In some embodiments, a gNB-CU of the gNB 511 may host the RRC 1155, SDAP 1147, and PDCP 1140 of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 511 may each host the RLC 1130, MAC 1120, and PHY 1110 of the gNB 511.

In a first example, a control plane protocol stack may comprise, in order from highest layer to lowest layer, NAS 1157, RRC 1155, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110. In this example, upper layers 1160 may be built on top of the NAS 1157, which includes an IP layer 1161, an SCTP 1162, and an application layer signaling protocol (AP) 1163.

In NR implementations, the AP 1163 may be an NG application protocol layer (NGAP or NG-AP) 1163 for the NG interface 513 defined between the NG-RAN node 511 and the AMF 721, or the AP 1163 may be an Xn application protocol layer (XnAP or Xn-AP) 1163 for the Xn interface 512 that is defined between two or more RAN nodes 511.

The NG-AP 1163 may support the functions of the NG interface 513 and may comprise Elementary Procedures (EPs). An NG-AP EP may be a unit of interaction between the NG-RAN node 511 and the AMF 721. The NG-AP 1163 services may comprise two groups: UE-associated services (e.g., services related to a UE 501) and non-UE-associated services (e.g., services related to the whole NG interface instance between the NG-RAN node 511 and AMF 721). These services may include functions including, but not limited to: a paging function for the sending of paging requests to NG-RAN nodes 511 involved in a particular paging area; a UE context management function for allowing the AMF 721 to establish, modify, and/or release a UE context in the AMF 721 and the NG-RAN node 511; a mobility function for UEs 501 in ECM-CONNECTED mode for intra-system HOs to support mobility within NG-RAN and inter-system HOs to support mobility from/to EPS systems; a NAS Signaling Transport function for transporting or rerouting NAS messages between UE 501 and AMF 721; a NAS node selection function for determining an association between the AMF 721 and the UE 501; NG interface management function(s) for setting up the NG interface and monitoring for errors over the NG interface; a warning message transmission function for providing means to transfer warning messages via NG interface or cancel ongoing broadcast of warning messages; a Configuration Transfer function for requesting and transferring of RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes 511 via CN 520; and/or other like functions.

The XnAP 1163 may support the functions of the Xn interface 512 and may comprise XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may comprise procedures used to handle UE mobility within the NG RAN 511 (or E-UTRAN 610), such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The XnAP global procedures may comprise procedures that are not related to a specific UE 501, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, and the like.

In LTE implementations, the AP 1163 may be an S1 Application Protocol layer (S1-AP) 1163 for the S1 interface 513 defined between an E-UTRAN node 511 and an MME, or the AP 1163 may be an X2 application protocol layer (X2AP or X2-AP) 1163 for the X2 interface 512 that is defined between two or more E-UTRAN nodes 511.

The S1 Application Protocol layer (S1-AP) 1163 may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interaction between the E-UTRAN node 511 and an MME 621 within an LTE CN 520. The S1-AP 1163 services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

The X2AP 1163 may support the functions of the X2 interface 512 and may comprise X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may comprise procedures used to handle UE mobility within the E-UTRAN 520, such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The X2AP global procedures may comprise procedures that are not related to a specific UE 501, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, cell activation procedures, and the like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 1162 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 1162 may ensure reliable delivery of signaling messages between the RAN node 511 and the AMF 721/MME 621 based, in part, on the IP protocol, supported by the IP 1161. The Internet Protocol layer (IP) 1161 may be used to perform packet addressing and routing functionality. In some implementations the IP layer 1161 may use point-to-point transmission to deliver and convey PDUs. In this regard, the RAN node 511 may comprise L2 and L1 layer communication links (e.g., wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in order from highest layer to lowest layer, SDAP 1147, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110. The user plane protocol stack may be used for communication between the UE 501, the RAN node 511, and UPF 702 in NR implementations or an S-GW 622 and P-GW 623 in LTE implementations. In this example, upper layers 1151 may be built on top of the SDAP 1147, and may include a user datagram protocol (UDP) and IP security layer (UDP/IP) 1152, a General Packet Radio Service (GPRS) Tunneling Protocol for the user plane layer (GTP-U) 1153, and a User Plane PDU layer (UP PDU) 1163.

The transport network layer 1154 (also referred to as a “transport layer”) may be built on IP transport, and the GTP-U 1153 may be used on top of the UDP/IP layer 1152 (comprising a UDP layer and IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the “Internet layer”) may be used to perform packet addressing and routing functionality. The IP layer may assign IP addresses to user data packets in any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 1153 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP/IP 1152 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 511 and the S-GW 622 may utilize an S1-U interface to exchange user plane data via a protocol stack comprising an L1 layer (e.g., PHY 1110), an L2 layer (e.g., MAC 1120, RLC 1130, PDCP 1140, and/or SDAP 1147), the UDP/IP layer 1152, and the GTP-U 1153. The S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer 1152, and the GTP-U 1153. As discussed previously, NAS protocols may support the mobility of the UE 501 and the session management procedures to establish and maintain IP connectivity between the UE 501 and the P-GW 623.

Moreover, although not shown by FIG. 11, an application layer may be present above the AP 1163 and/or the transport network layer 1154. The application layer may be a layer in which a user of the UE 501, RAN node 511, or other network element interacts with software applications being executed, for example, by application circuitry 805 or application circuitry 905, respectively. The application layer may also provide one or more interfaces for software applications to interact with communications systems of the UE 501 or RAN node 511, such as the baseband circuitry 1010. In some implementations the IP layer and/or the application layer may provide the same or similar functionality as layers 5-7, or portions thereof, of the Open Systems Interconnection (OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—the presentation layer, and OSI Layer 5—the session layer).

FIG. 12 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 12 shows a diagrammatic representation of hardware resources 1200 including one or more processors (or processor cores) 1210, one or more memory/storage devices 1220, and one or more communication resources 1230, each of which may be communicatively coupled via a bus 1240. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1202 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1200.

The processors 1210 may include, for example, a processor 1212 and a processor 1214. The processor(s) 1210 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 1220 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1220 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 1230 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1204 or one or more databases 1206 via a network 1208. For example, the communication resources 1230 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 1250 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1210 to perform any one or more of the methodologies discussed herein. The instructions 1250 may reside, completely or partially, within at least one of the processors 1210 (e.g., within the processor's cache memory), the memory/storage devices 1220, or any suitable combination thereof. Furthermore, any portion of the instructions 1250 may be transferred to the hardware resources 1200 from any combination of the peripheral devices 1204 or the databases 1206. Accordingly, the memory of processors 1210, the memory/storage devices 1220, the peripheral devices 1204, and the databases 1206 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

Example Procedures

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of FIGS. 5-12, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in FIG. 13. For example, the process 1300 may include: generating, by the UE, an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace, as shown in step 1302. The method can further include transmitting, by the UE, the uplink signal over a PUCCH that utilizes unlicensed spectrum in a new radio wireless network, as shown in step 1304.

In embodiments, the process 1300 further comprises determining, by the UE, a value of “n” based on an uplink control information (UCI) payload size, choosing, by the UE, a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.

In embodiments, the process 1300 further comprises receiving, by the UE, one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRB s per interlace.

In embodiments, the process 1300 further comprises receiving the generating further comprises determining, by the UE, a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.

In embodiments, the process 1300 further comprises receiving further comprises configuring, by the UE, a starting interlace and a number of interlaces as a PUCCH resource allocation for PUCCH format 2 in a frequency domain.

In embodiments, the process 1300 further comprises receiving the generating further comprises determining, by the UE, a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int). In embodiments, Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.

In embodiments, the steps and/or functions of process 1300 can be at least partially performed by application circuitry 805 or 905, baseband circuitry 810 or 910, and/or processor(s) 1210.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

As described above, aspects of the present technology may include the gathering and use of data available from various sources, e.g., to improve or enhance functionality. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, Twitter ID's, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. The present disclosure recognizes that the use of such personal information data, in the present technology, may be used to the benefit of users.

The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should only occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of, or access to, certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, the present technology may be configurable to allow users to selectively “opt in” or “opt out” of participation in the collection of personal information data, e.g., during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Therefore, although the present disclosure may broadly cover use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.

EXAMPLES

Therefore, although the present disclosure may broadly cover use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.

Example A01 includes a method of wireless communication for a fifth generation (5G) new radio (NR) system operating in unlicensed spectrum (NR-unlicensed), the method comprising: determining, by a UE, time, frequency, and code domain resources to be used for the transmission of physical uplink control channel (PUCCH), based on different PUCCH formats, in accordance with the regulatory requirements associated with the usage of unlicensed spectrum; and transmitting, by the UE, one or more uplink signals using one of the PUCCH formats on physical uplink control channel using unlicensed spectrum.

Example A02 includes the method of example A01 and/or some other example(s) herein, wherein the UE is configured by higher layer signaling (for example, by RRC configuration) with PUCCH format 2 having n number of PRBs which are mapped non-contiguously (e.g., in interlaced manner) across frequency domain on each OFDM symbol, so as to meet the OCB criteria.

Example A03 includes the method of example A02 and/or some other example(s) herein, wherein n is an integer multiple of number of PRBs per interlace, wherein the UE always uses an integer number of full interlaces, depending in the determined value of n based on UCI payload size, and UE may choose a code rate less than the configured maximum code rate in order to determine the appropriate value of n that is divisible by number of PRBs per interlace, wherein frequency domain resources provided to the UE via higher layer signaling can include interlace indices, where each interlace with certain index number i can be pre-defined in the specification in terms of starting PRB, inter-PRB separation and number-of-PRBs per interlace, wherein a bitmap based approach is used to indicate which interlaces to be used, wherein alternatively, higher layer signaling only indicates the interlace index of the first interlace and the subsequent interlace indices to be used are derived implicitly by some pre-defined rules, wherein the index of the first interlace to be used is indicated by either bitmap or by k bits, where k=┌log₂(x_(int) ^(max))┐, x_(int) ^(max) being maximum number of interlaces.

Example A04 includes the method of example A03 and/or some other example(s) herein, wherein certain combinations of interlaces to be used for frequency allocation of PUCCH format 2 (and 3) can be predefined, wherein assuming maximally 2 full interlaces are used for PUCCH format 2, and totally 5 interlaces are defined, then the combinations can be defined as 0, 1, 2, 3, 4 for one interlace case, {0 2}, {1, 3}, {0, 1} {1, 2}, {2,3} {3,4} for two full interlace case.

Example A05 includes the method of example A03 and/or some other example(s) herein, wherein the starting interlace and the number of interlaces can be configured as PUCCH resource allocation for PUCCH format 2 (and 3) in frequency domain, wherein the bitwidth may depend on the maximum number of interlaces regardless of the numerology configured for the UL bandwidth part (BWP) or depend on the number of interlaces within 20 MHz in accordance with the configured numerology for UL BWP.

Example A06 includes the method of example A02 and/or some other example(s) herein, wherein n is not be an integer multiple of number of PRBs per interlace, e.g., n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), where Δ_(PRB)<y_(PRB) ^(int), wherein there are certain restrictions applied on the permissible values of Δ_(PRB) depending on the allowed resource allocation unit granularity beyond an integer number of full interlace allocations, wherein these excess Δ_(PRB) are mapped on the same interlace index (e.g., consecutive or non-consecutive Δ_(PRB) PRBs corresponding to a single interlace index i) or on more than one interlaces, wherein frequency domain resources provided to the UE via higher layer signalling include interlace indices for full interlace allocations as mentioned in the examples 3 to 5 and an additional one bit signalling that indicates if a non-zero Δ_(PRB) is allowed or not, wherein depending on the value of this bit, UE either implicitly derives the locations of Δ_(PRB) PRBs on one or more interlaces based on some pre-defined rule or the locations of Δ_(PRB) excess PRBs are explicitly signalled to the UE by higher layer signalling, or a combination thereof.

Example A07 includes the method of example A06 and/or some other example(s) herein, wherein Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1, wherein as one example, for y_(PRB) ^(int)=10, Δ_(PRB)={2,5}, wherein the UE can choose a code rate less than the configured maximum code rate in order to determine the appropriate value of n such that, in case it is not divisible by y_(PRB) ^(int), the excess Δ_(PRB) PRBs would be a factor of y_(PRB) ^(int), wherein in addition to full interlaces, resource allocation units are in terms of partial interlace, which contains y_(PRB) ^(partial) number of PRBs, where y_(PRB) ^(partial) is a factor of y_(PRB) ^(int), wherein such partial interlaces are either predefined in the specification and UE is either explicitly indicated by higher layer signaling all the indices of full and partial interlaces to be used, or UE derives implicitly these full and partial interlace indices based on the first interlace index provided by higher layer signaling, using some pre-defined rules, or a combination thereof.

Example A08 includes the method of example A06 and/or some other example(s) herein, wherein Δ_(PRB) is not restricted to be a factor of y_(PRB) ^(int), e.g., the UE can determine any value of n depending on its payload size and maximum configured code rate, which can potentially result in Δ_(PRB)>0, not necessarily a factor of y_(PRB) ^(int), wherein the frequency allocation of these excess Δ_(PRB) PRBs is either explicitly indicated to the UE by higher layer signaling, or is implicitly derived based on some pre-defined rules (which may be a function of the allocated full interlace indices) or a combination thereof.

Example A09 includes the method of example A02 and/or some other example(s) herein, wherein for N-symbol NR PUCCH format 2, where N>1 (e.g., N=2), similar enhancements as mentioned in examples 3 through 8 can be applied, where the same frequency domain resource allocation on one symbol is repeated across N symbols of PUCCH format 2.

Example A10 includes the method of example A02 and/or some other example(s) herein, wherein for N-symbol NR PUCCH format 2/3, where N>1, frequency hopping is always disabled, since frequency diversity is already achieved by interlace based resource allocation.

Example All includes the method of example A01 and/or some other example(s) herein, wherein wherein a UE is configured by higher layer signaling (for example, by RRC configuration) with PUCCH format 3 having n number of PRBs which are mapped non-contiguously (e.g., in interlaced manner) across frequency domain on each OFDM symbol, so as to meet the OCB criteria, wherein the frequency domain resource enhancements in examples 3 through 8 are applicable to PUCCH format 3 as well, with the additional restriction that n=2^(a)*3^(b)*5^(c) for DFT-s-OFDM based PUCCH format 3, or if CP-OFDM is used for interlace based enhanced PUCCH format 3, the restriction on n is relaxed.

Example A12 includes the method of example A11 and/or some other example(s) herein, wherein for N-symbol NR PUCCH format 3 (4≤N≤14), frequency hopping is made always disabled, since frequency diversity can already be achieved by interlace based resource allocation.

Example A13 includes the method of example A11 and/or some other example(s) herein, wherein time domain structure of enhanced PUCCH format 3, e.g., the TDM pattern of UCI and DMRS symbols is modified from NR PUCCH format 3 so as to facilitate early/fast detection of transmission at gNB side, since in unlicensed band, the channel access is based on listen-before-talk (LBT) and hence UE's transmission is subject to clear channel assessment (CCA) success, wherein only the first DMRS symbol for PUCCH format 3 are shifted to the first symbol, wherein for PUCCH format 3 with 6 symbol duration, symbol {1,4} are allocated for DMRS, wherein new DMRS position is symbol {0,4}, wherein all the DMRS symbols are shifted left accordingly so that the first symbol is allocated for DMRS symbol, wherein for PUCCH format 3 with 6 symbol duration, symbol {1,4} are allocated for DMRS, wherein new DMRS position is symbol {0,3}.

Example A14 includes the method of example A03 and/or some other example(s) herein, wherein length-n_(UE) orthogonal cover codes (OCCs) are applied on n_(RS) DMRS and n_(UCI) UCI symbols FDM'd on each PRB of interlace based PUCCH format 2, respectively, wherein n_(UE) users are code domain multiplexed on the same time—frequency resources using OCCs on DMRS and UCI symbols on each PRB, where n_(UE)≤min{n_(RS), n_(UCI)} and n_(UE) is a common factor of n_(RS) and n_(UCI).

Example A15 includes the method of example A14 and/or some other example(s) herein, wherein the OCCs applied on UCI symbols are the same codes as that applied on DMRS symbols, wherein DFT based OCCs can be applied on both UCI and DMRS symbols, when there is no restriction on n_(UE), wherein if n_(UE) can be expressed as power of 2 (e.g., 2^(x), x being an integer), then Walsh-code based OCC can be used for both DMRS and UCI symbols.

Example A16 includes the method of example A15 and/or some other example(s) herein, wherein different OCCs may be applied on DMRS and UCI symbols, wherein DMRS OCC may be based on Walsh-code whereas UCI-OCC may be based on DFT-code and vice versa.

Example A17 includes the method of example A14 and/or some other example(s) herein, wherein in addition to frequency domain OCC on each PRB, time domain OCC is applied across OFDM symbols if N>1, wherein either the same OCC applied across frequency domain is applied across time domain, or different time domain OCC is used.

Example A18 includes the method of example A14 and/or some other example(s) herein, wherein on each PRB, the OCC indices applied to multiplexed UEs are different in order to randomize the OCC pattern over all PRBs and reduce resulting peak-to-average power ratio (PAPR).

Example A19 includes the method of example A18 and/or some other example(s) herein, wherein for length-x OCC applied on DMRS and UCI symbols on each PRB, the OCC indices used for UE1, . . . , UE(x) on 1^(st) PRB can be {C₀, C₁, . . . , C_(x−1)} respectively, whereas on i^(th) PRB, the OCC indices used may be {C_((i−1)modx), C_((imodx)), . . . , C_((i+x−2)modx)} respectively.

Example A20 includes the method of example A18 and/or some other example(s) herein, wherein the OCC indices used by one UE on 1^(st) PRB is incremented by a UE-specific offset value on every subsequent PRBs on one or more interlace(s) assigned to the UE, which is provided by higher layer signaling.

Example A21 includes the method of example A18 and/or some other example(s) herein, wherein the OCC randomization patterns used for DMRS symbols and UCI symbols are same or different, wherein the OCC randomization is defined as a function of one or more of the following parameters: physical or virtual cell ID, symbol/slot/frame index, etc., wherein the OCC randomization is applied for the PUCCH format 3 enhancement when OCC is applied for the transmission of UCI, which can help reduce PAPR.

Example A22 includes the method of example A14 and/or some other example(s) herein, wherein instead of OCC pattern randomization, symbol level scrambling is used on UCI symbols after applying OCC to minimize PAPR, wherein the same OCC index or different OCC index is used for a UE on all PRBs, wherein QPSK modulation is employed after the pseudo noise (PN) sequence generation, wherein the symbol level scrambling may be cell specific or UE specific, wherein the initialization of scrambling sequence may be defined as one or more following parameters: physical or virtual cell ID, symbol/slot/frame index, UE ID (e.g., C-RNTI), etc., wherein the PN sequence can be initialized as C_(init)=n_(ID), wherein when n_(ID)=n_(ID) ^(cell), same scrambling sequence can be generated, which is mainly for PAPR reduction, wherein the symbol level scrambling may be also applied for the PUCCH format 3 enhancement when OCC is applied for the transmission of UCI, which can help reduce PAPR.

Example A23 includes the method of example A14 and/or some other example(s) herein, wherein different UEs are multiplexed on interlace based PUCCH format 2 either in frequency division multiplexing manner (e.g., on different interlaces) or time division multiplexing manner (e.g., on different OFDM symbols within a slot) only and code domain multiplexing is not allowed.

Example A24 includes the method of example A14 and/or some other example(s) herein, wherein the OCC applied for the transmission of DMRS is implicitly derived from the OCC for the transmission of UCI symbols for PUCCH format 2, wherein a same OCC index is applied for the transmission of DMRS and UCI symbols.

Example A25 includes the method of example A11 and/or some other example(s) herein, wherein CDM based UE multiplexing is enabled on enhanced interlace based PUCCH format 3 by extending the pre-DFT block-wise OCC spreading (applied on single PRB in Rel-15 NR PUCCH format 4) to all PRBs on one or more interlaces assigned to enhanced PUCCH format 3, wherein by extending pre-DFT OCC block-wise to all PRBs, UCI symbols of each multiplexed UEs are mapped on orthogonal combs and hence, irrespective of channel delay spread the orthogonality between transmissions of different UEs retains.

Example A26 includes the method of example A25 and/or some other example(s) herein, wherein on top of pre-DFT OCC, time domain OCC is applied where the OCC may be the same as the pre-DFT OCC (before blockwise spreading) or different OCC.

Example A27 includes the method of example A25 and/or some other example(s) herein, wherein the cyclic shift for the transmission of DMRS is configured as part of PUCCH resource for PUCCH format 3, wherein the cyclic shift for the transmission of DMRS is implicitly derived from the pre-DFT OCC index for the transmission of UCI symbols for PUCCH format 3, wherein assuming the number of cyclic shifts for DMRS as N_(CS), and the number of pre-DFT OCC index as N_(OCC), then the cyclic shift index is derived as

${I_{cs} = {\frac{N_{cs}}{N_{occ}} \cdot I_{occ}}},$

wherein assuming 12 cyclic shifts for DMRS and 4 pre-DFT OCCs, the pre-DFT OCC index as {0,1,2,3}, then the corresponding cyclic shift index is {0,3,6,9}.

Example B01 includes a method of wireless communication in unlicensed spectrum, the method comprising: determining or causing to determine time, frequency, and code domain resources to be used for a physical uplink control channel (PUCCH) transmission in the unlicensed spectrum based on different PUCCH formats; and transmitting or causing to transmit one or more uplink signals on the PUCCH in the unlicensed spectrum using a PUCCH format of the different PUCCH formats.

Example B02 includes the method of example B01 and/or some other example(s) herein, further comprising: receiving a message via higher layer signaling; and determining or causing to determine, based on the message, a configuration indicating a PUCCH format 2 having n number of physical resorce blocks (PRBs), the n number of PRBs being mapped non-contiguously in an interlaced manner across a frequency domain on each OFDM symbol to meet Occupied Channel Bandwidth (OCB) criteria.

Example B03 includes the method of example B02 and/or some other example(s) herein, wherein n is an integer multiple of a number of PRBs per interlace, and the method comprises: using or causing to use an integer number of full interlaces based on a determined value of n and based on uplink control information (UCI) payload size; selecting or causing to select a code rate less than a configured maximum code rate in order to determine the value of n that is divisible by the number of PRBs per interlace.

Example B04 includes the method of example B03 and/or some other example(s) herein, further comprising: determining or causing to determine, based on the configuration or another configuration obtained via higher layer signaling, frequency domain resources including interlace indices, where an interlace index i can be pre-defined based on a starting PRB, inter-PRB separation, and/or a number of PRBs per interlace.

Example B05 includes the method of example B04 and/or some other example(s) herein, further comprising: determining or causing to determine interlaces to be used based on an obtained bitmap.

Example B06 includes the method of example B04 and/or some other example(s) herein, further comprising: determining or causing to determine, based on the configuration or another configuration obtained via higher layer signaling, an interlace index of a first interlace; and deriving or causing to derive subsequent interlace indices to be used implicitly by pre-defined rule(s), wherein the interlace index of the first interlace is indicated either by a bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐, wherein x_(int) ^(max) is a maximum number of interlaces.

Example B07 includes the method of examples B03-B06 and/or some other example(s) herein, wherein one or more combinations of interlaces to be used for frequency allocation of PUCCH format 2 (and 3) are predefined.

Example B08 includes the method of example B07 and/or some other example(s) herein, wherein, when a maximum of two full interlaces are used for PUCCH format 2 and a total of five interlaces are defined, then the one or more combinations include 0, 1, 2, 3, 4 for one interlace case and {0 2}, {1, 3}, {0, 1} {1, 2}, {2,3} {3,4} for two full interlace case.

Example B09 includes the method of examples B03-B06 and/or some other example(s) herein, wherein a starting interlace and a number of interlaces can be configured as PUCCH resource allocation for PUCCH format 2 (and 3) in frequency domain, wherein a bitwidth depends on a maximum number of interlaces regardless of a numerology configured for the uplink (UL) bandwidth part (BWP) or depends on a number of interlaces within 20 MHz in accordance with a configured numerology for UL BWP.

Example B10 includes the method of example B02 and/or some other example(s) herein, wherein n is not be an integer multiple of a number of PRBs per interlace, wherein n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), and Δ_(PRB)<y_(PRB) ^(int).

Example B10.5 includes the method of example B10 and/or some other example(s) herein, wherein values of Δ_(PRB) depend on an allowed resource allocation unit granularity beyond an integer number of full interlace allocations, and wherein excess Δ_(PRB) are mapped on a same interlace index including consecutive or non-consecutive Δ_(PRB) PRBs corresponding to a single interlace index i or on more than one of the interlaces.

Example B11 includes the method of example B10.5 and/or some other example(s) herein, further comprising: determining or causing to determine, based on the configuration or another configuration obtained via higher layer signaling, frequency domain resources including interlace indices for full interlace allocations as mentioned in the examples B03 to B09 and an additional one bit signalling that indicates if a non-zero Δ_(PRB) is allowed or not; and depending on a value of the bit, one or both of: implicitly deriving or causing to implicitly derive locations of Δ_(PRB) PRBs on one or more interlaces based on some pre-defined rule; and determining or causing to determine the locations of the excess Δ_(PRB) PRBs when explicitly signalled via higher layer signalling.

Example B12 includes the method of examples B10.5-B11 and/or some other example(s) herein, wherein Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.

Example B13 includes the method of example B12 and/or some other example(s) herein, wherein y_(PRB) ^(int)=10 and Δ_(PRB)={2,5}, and the method comprises: selecting or causing to select a code rate less than a configured maximum code rate to determine a value of n such that the excess Δ_(PRB) PRBs are a factor of y_(PRB) ^(int) in case it is not divisible y_(PRB) ^(int).

Example B14 includes the method of example B13 and/or some other example(s) herein, wherein resource allocation units are defined in terms of both full interlaces and partial interlaces, wherein the partial interlaces include y_(PRB) ^(partial) number of PRBs, wherein y_(PRB) ^(partial) is a factor of y_(PRB) ^(int).

Example B15 includes the method of example B14 and/or some other example(s) herein, wherein the partial interlaces are either predefined or explicitly indicated via higher layer signaling, wherein the explicit indications indicated via higher layer signaling include some or all indices of full interlaces and partial interlaces to be used.

Example B16 includes the method of example B14 and/or some other example(s) herein, further comprising: implicitly deriving or causing to implicitly derive full interlace indices and partial interlace indices based on a first interlace index obtained via higher layer signaling and/or using pre-defined rule(s).

Example B17 includes the method of examples B09-B11 and/or some other example(s) herein, wherein Δ_(PRB) is not restricted to be a factor of y_(PRB) ^(int), and the method comprises: determining or causing to determine a value of n depending on a payload size and a maximum configured code rate, wherein Δ_(PRB)>0 and is not necessarily a factor of y_(PRB) ^(int).

Example B18 includes the method of example B17 and/or some other example(s) herein further comprising: determining or causing to determine a frequency allocation of the excess Δ_(PRB) PRBs based on explicit indications obtained via higher layer signaling; implicitly deriving or causing to implicitly derive the frequency allocation of the excess Δ_(PRB) PRBs based on pre-defined rule(s) and/or based on a function of allocated full interlace indices.

Example B19 includes the method of example B02 and/or some other example(s) herein, wherein the method of examples B03-B18 are applied to N-symbol NR PUCCH format 2, wherein N>1 and/or N=2), wherein a same frequency domain resource allocation on one symbol is repeated across N symbols of PUCCH format 2.

Example B20 includes the method of example B02 and/or some other example(s) herein, wherein, for N-symbol NR PUCCH format 2/3, where N>1, frequency hopping is disabled.

Example B21 includes the method of example B01 and/or some other example(s) herein, further comprising: receiving a message via higher layer signaling; and determining or causing to determine, based on the message, a configuration indicating a PUCCH format 3 having n number of PRBs, the n number of PRBs being mapped non-contiguously in an interlaced manner across a frequency domain on each OFDM symbol to meet OCB criteria.

Example B22 includes the method of example B21 and/or some other example(s) herein, wherein the frequency domain resource enhancements of examples B03-B18 are applied to PUCCH format 3 including a restriction of n=2^(a)*3^(b)*5^(c) for DFT-s-OFDM based PUCCH format 3, or the restriction on n is relaxed if CP-OFDM is used for interlace based enhanced PUCCH format 3.

Example B23 includes the method of example B22 and/or some other example(s) herein, wherein for N-symbol NR PUCCH format 3 (4≤N≤14), frequency hopping is disabled.

Example B24 includes the method of example B22 and/or some other example(s) herein, wherein a time domain structure of enhanced PUCCH format 3 is modified from NR PUCCH format 3 to facilitate early/fast detection of transmission, wherein the time domain structure of enhanced PUCCH format 3 includes a TDM pattern of UCI and DMRS symbols.

Example B25 includes the method of example B24 and/or some other example(s) herein, wherein only a first DMRS symbol for PUCCH format 3 is shifted to a first symbol.

Example B26 includes the method of example B25 and/or some other example(s) herein, wherein, for PUCCH format 3 with a 6 symbol duration, symbol {1,4} is allocated for DMRS and a new DMRS position is symbol {0,4}.

Example B27 includes the method of example B24 and/or some other example(s) herein, wherein, all DMRS symbols are shifted left accordingly so that a first symbol is allocated for a DMRS symbol.

Example B28 includes the method of example B27 and/or some other example(s) herein, wherein, for PUCCH format 3 with a 6 symbol duration, symbol {1,4} is allocated for the DMRS and a new DMRS position is symbol {0,3}.

Example B29 includes the method of examples B03-B06 and/or some other example(s) herein, further comprising: applying or causing to apply orthogonal cover codes (OCCs) of length-n_(UE) on n_(RS) DMRS and n_(UCI) UCI symbols FDM'd on each PRB of interlace based PUCCH format 2, respectively, wherein n_(UE) users are code domain multiplexed on the same time-frequency resources using OCCs on DMRS and UCI symbols on each PRB, where n_(UE)≤min{n_(RS), n_(UCI)} and n_(UE) is a common factor of n_(RS) and n_(UCI).

Example B30 includes the method of example B29 and/or some other example(s) herein, wherein the OCCs applied on UCI symbols are same codes as those applied on DMRS symbols, wherein DFT based OCCs are applied on both UCI and DMRS symbols when there is no restriction on n_(UE), and Walsh-code based OCC are applied on both DMRS and UCI symbols when n_(UE) can be expressed as power of 2.

Example B31 includes the method of example B30 and/or some other example(s) herein, further comprising: applying or causing to apply different OCCs on DMRS and UCI symbols, wherein DMRS OCCs are based on Walsh-codes whereas UCI-OCCs are based on DFT-codes, and/or vice versa.

Example B32 includes the method of examples B29-B30 and/or some other example(s) herein, wherein a time domain OCC is applied across OFDM symbols if N>1 in addition to frequency domain OCC on each PRB, wherein same OCCs applied across frequency domain are applied across the time domain or different time domain OCCs are applied across the time domain.

Example B33 includes the method of examples B29-B30 and/or some other example(s) herein, wherein on each PRB, the OCC indices applied to multiplexed UEs are different in order to randomize the OCC pattern over all PRBs and reduce resulting peak-to-average power ratio (PAPR).

Example B34 includes the method of example B33 and/or some other example(s) herein, wherein for length-x OCC applied on DMRS and UCI symbols on each PRB, the OCC indices used for UE1, . . . , UE(x) on 1^(st) PRB can be {C₀, C₁, . . . , C_(x−1)} respectively, whereas on i^(th) PRB, the OCC indices used may be {C_((i−1)modx), C_((imodx)), . . . , C_((i+x−2)modx)} respectively.

Example B35 includes the method of example B33 and/or some other example(s) herein, wherein the OCC indices used by one UE on a 1^(st) PRB is incremented by a UE-specific offset value on every subsequent PRBs on one or more interlace(s) assigned to the UE, which is provided by higher layer signaling.

Example B36 includes the method of example B33 and/or some other example(s) herein, wherein OCC randomization patterns used for DMRS symbols and UCI symbols are same or different.

Example B37 includes the method of example B36 and/or some other example(s) herein, wherein the OCC randomization is defined as a function of one or more of a physical cell identifier (ID, a virtual cell ID, and a symbol/slot/frame index.

Example B38 includes the method of example B37 and/or some other example(s) herein, wherein the OCC randomization is applied to the PUCCH format 3 when OCC is applied for transmission of UCI.

Example B39 includes the method of examples B29-B30 and/or some other example(s) herein, wherein symbol level scrambling is used on UCI symbols after applying OCC to minimize PAPR.

Example B40 includes the method of example B39 and/or some other example(s) herein, wherein a same OCC index or a different OCC index is used on all PRBs.

Example B41 includes the method of example B40 and/or some other example(s) herein, wherein QPSK modulation is employed after the pseudo noise (PN) sequence generation.

Example B42 includes the method of example B41 and/or some other example(s) herein, wherein symbol level scrambling is cell-specific or UE-specific.

Example B43 includes the method of example B42 and/or some other example(s) herein, wherein initialization of a scrambling sequence is defined as one or more of: a physical cell ID, a virtual cell ID, a symbol/slot/frame index, and a UE ID.

Example B44 includes the method of example B43 and/or some other example(s) herein, wherein the UE ID is a C-RNTI.

Example B45 includes the method of example B44 and/or some other example(s) herein, wherein a PN sequence is initialized as C_(init)=n_(ID), wherein when n_(ID)=n_(ID) ^(cell), a same scrambling sequence is generated.

Example B46 includes the method of example B45 and/or some other example(s) herein, wherein symbol level scrambling is applied for the PUCCH format 3 when OCC is applied for the transmission of.

Example B47 includes the method of examples B29-B30 and/or some other example(s) herein, wherein different UEs are multiplexed on interlace based PUCCH format 2 either in a frequency division multiplexing manner or in a time division multiplexing manner only and code domain multiplexing is not allowed.

Example B48 includes the method of examples B29-B30 and/or some other example(s) herein, wherein different UEs are multiplexed on interlace based PUCCH format 2 either on different interlaces or on different OFDM symbols within a slot only and code domain multiplexing is not allowed.

Example B49 includes the method of examples B29-B30 and/or some other example(s) herein, wherein an OCC applied for a transmission of DMRS is implicitly derived from the OCC for the transmission of UCI symbols for PUCCH format 2.

Example B50 includes the method of example B49 and/or some other example(s) herein, wherein a same OCC index is applied for the transmission of DMRS and UCI symbols.

Example B51 includes the method of examples B21-B22 and/or some other example(s) herein, wherein CDM based UE multiplexing is enabled on enhanced interlace based PUCCH format 3 by extending a pre-DFT block-wise OCC spreading to all PRBs on one or more interlaces assigned to enhanced PUCCH format 3.

Example B52 includes the method of example B51 and/or some other example(s) herein, wherein the pre-DFT block-wise OCC spreading is applied on single PRB in Rel-15 NR PUCCH format 4.

Example B53 includes the method of examples B51-B52 and/or some other example(s) herein, wherein UCI symbols of each multiplexed UEs are mapped on orthogonal combs, and irrespective of channel delay spread the orthogonality between transmissions of different UEs retains.

Example B54 includes the method of examples B51-B53 and/or some other example(s) herein, wherein on top of pre-DFT OCC, a time domain OCC is applied where the OCC is same as the pre-DFT OCC before blockwise spreading or is a different OCC.

Example B55 includes the method of examples B51-B53 and/or some other example(s) herein, wherein a cyclic shift for transmission of DMRS is configured as part of PUCCH resource for PUCCH format 3.

Example B56 includes the method of example B55 and/or some other example(s) herein, wherein the cyclic shift for the transmission of DMRS is implicitly derived from the pre-DFT OCC index for the transmission of UCI symbols for PUCCH format 3.

Example B57 includes the method of examples B55-B56 and/or some other example(s) herein, wherein the cyclic shift index is derived as

${I_{cs} = {\frac{N_{cs}}{N_{occ}} \cdot I_{occ}}},$

wherein N_(CS) is a number of cyclic shifts for DMRS and N_(OCC) is a number of pre-DFT OCC index.

Example B58 includes the method of example B57and/or some other example(s) herein, wherein the pre-DFT OCC index is {0,1,2,3} and the cyclic shift index is {0,3,6,9} when there are twelve cyclic shifts for DMRS and four pre-DFT OCCs.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples A01-A27, B01-B58, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples A01-A27, B01-B58, or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples A01-A27, B01-B58, or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples A01-A27, B01-B58, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A27, B01-B58, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples A01-A27, B01-B58, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A27, B01-B58, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples A01-A27, B01-B58, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A27, B01-B58, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A27, B01-B58, or portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples A01-A27, B01-B58, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations

For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein, but are not meant to be limiting.

-   -   3GPP Third Generation Partnership Project     -   4G Fourth Generation     -   5G Fifth Generation     -   5GC 5G Core network     -   ACK Acknowledgement     -   AF Application Function     -   AM Acknowledged Mode     -   AMBR Aggregate Maximum Bit Rate     -   AMF Access and Mobility Management Function     -   AN Access Network     -   ANR Automatic Neighbour Relation     -   AP Application Protocol, Antenna Port, Access Point     -   API Application Programming Interface     -   APN Access Point Name     -   ARP Allocation and Retention Priority     -   ARQ Automatic Repeat Request     -   AS Access Stratum     -   ASN.1 Abstract Syntax Notation One     -   AUSF Authentication Server Function     -   AWGN Additive White Gaussian Noise     -   BCH Broadcast Channel     -   BER Bit Error Ratio     -   BFD Beam Failure Detection     -   BLER Block Error Rate     -   BPSK Binary Phase Shift Keying     -   BRAS Broadband Remote Access Server     -   BSS Business Support System     -   BS Base Station     -   BSR Buffer Status Report     -   BW Bandwidth     -   BWP Bandwidth Part     -   C-RNTI Cell Radio Network Temporary Identity     -   CA Carrier Aggregation, Certification Authority     -   CAPEX CAPital EXpenditure     -   CBRA Contention Based Random Access     -   CC Component Carrier, Country Code, Cryptographic Checksum     -   CCA Clear Channel Assessment     -   CCE Control Channel Element     -   CCCH Common Control Channel     -   CE Coverage Enhancement     -   CDM Content Delivery Network     -   CDMA Code-Division Multiple Access     -   CFRA Contention Free Random Access     -   CG Cell Group     -   CI Cell Identity     -   CID Cell-ID (e.g., positioning method)     -   CIM Common Information Model     -   CIR Carrier to Interference Ratio     -   CK Cipher Key     -   CM Connection Management, Conditional Mandatory     -   CMAS Commercial Mobile Alert Service     -   CMD Command     -   CMS Cloud Management System     -   CO Conditional Optional     -   CoMP Coordinated Multi-Point     -   CORESET Control Resource Set     -   COT Channel Occupancy Time     -   COTS Commercial Off-The-Shelf     -   CP Control Plane, Cyclic Prefix, Connection Point     -   CPD Connection Point Descriptor     -   CPE Customer Premise Equipment     -   CPICH Common Pilot Channel     -   CQI Channel Quality Indicator     -   CPU CSI processing unit, Central Processing Unit     -   C/R Command/Response field bit     -   CRAN Cloud Radio Access Network, Cloud RAN     -   CRB Common Resource Block     -   CRC Cyclic Redundancy Check     -   CRI Channel-State Information Resource Indicator, CSI-RS         Resource Indicator     -   C-RNTI Cell RNTI     -   CS Circuit Switched     -   CSAR Cloud Service Archive     -   CSI Channel-State Information     -   CSI-IM CSI Interference Measurement     -   CSI-RS CSI Reference Signal     -   CSI-RSRP CSI reference signal received power     -   CSI-RSRQ CSI reference signal received quality     -   CSI-SINR CSI signal-to-noise and interference ratio     -   CSMA Carrier Sense Multiple Access     -   CSMA/CA CSMA with collision avoidance     -   CSS Common Search Space, Cell-specific Search Space     -   CTS Clear-to-Send     -   CW Codeword     -   CWS Contention Window Size     -   D2D Device-to-Device     -   DC Dual Connectivity, Direct Current     -   DCI Downlink Control Information     -   DF Deployment Flavour     -   DL Downlink     -   DMTF Distributed Management Task Force     -   DPDK Data Plane Development Kit     -   DM-RS, DMRS Demodulation Reference Signal     -   DN Data network     -   DRB Data Radio Bearer     -   DRS Discovery Reference Signal     -   DRX Discontinuous Reception     -   DSL Domain Specific Language. Digital Subscriber Line     -   DSLAM DSL Access Multiplexer     -   DwPTS Downlink Pilot Time Slot     -   E-LAN Ethernet Local Area Network     -   E2E End-to-End     -   ECCA extended CCA     -   ECCE Enhanced CCE     -   ED Energy Detection     -   EDGE Enhanced Datarates for GSM Evolution (GSM Evolution)     -   EGMF Exposure Governance Management Function     -   EGPRS Enhanced GPRS     -   EIR Equipment Identity Register     -   EIRP Effective Isotropic Radiated Power, Equivalent Isotropic         Radiated Power     -   eLAA enhanced LAA     -   EM Element Manager     -   eMBB Enhanced Mobile Broadband     -   EMS Element Management System     -   eNB evolved NodeB, E-UTRAN Node B     -   EN-DC E-UTRA-NR Dual Connectivity     -   EPC Evolved Packet Core     -   EPDCCH enhanced PDCCH     -   EPRE Energy per resource element     -   EPS Evolved Packet System     -   ERP Effective Radiated Power, Equivalent Radiated Power     -   EREG enhanced REG     -   ETSI European Telecommunications Standards Institute     -   ETWS Earthquake and Tsunami Warning System     -   eUICC embedded UICC, embedded Universal Integrated Circuit Card     -   E-UTRA Evolved UTRA     -   E-UTRAN Evolved UTRAN     -   EV2X Enhanced V2X     -   F1AP F1 Application Protocol     -   F1-C F1 Control plane interface     -   F1-U F1 User plane interface     -   FACCH Fast Associated Control CHannel     -   FACCH/F Fast Associated Control Channel/Full rate     -   FACCH/H Fast Associated Control Channel/Half rate     -   FACH Forward Access Channel     -   FAUSCH Fast Uplink Signalling Channel     -   FB Functional Block     -   FBI Feedback Information     -   FCC Federal Communications Commission     -   FCCH Frequency Correction CHannel     -   FDD Frequency Division Duplex     -   FDM Frequency Division Multiplex     -   FDMA Frequency Division Multiple Access     -   FE Front End     -   FEC Forward Error Correction     -   FFS For Further Study     -   FFT Fast Fourier Transformation     -   feLAA further enhanced LAA     -   FN Frame Number     -   FPGA Field-Programmable Gate Array     -   FR Frequency Range     -   G-RNTI GERAN Radio Network Temporary Identity     -   GERAN GSM EDGE RAN, GSM EDGE Radio Access Network     -   GGSN Gateway GPRS Support Node     -   GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.:         Global Navigation Satellite System)     -   gNB Next Generation NodeB     -   gNB-CU gNB-centralized unit, Next Generation NodeB centralized         unit     -   gNB-DU gNB-distributed unit, Next Generation NodeB distributed         unit     -   GNSS Global Navigation Satellite System     -   GPRS General Packet Radio Service     -   GSM Global System for Mobile Communications, Groupe Special         Mobile     -   GTP GPRS Tunneling Protocol     -   GTP-U GPRS Tunnelling Protocol for User Plane     -   GTS Go To Sleep Signal (related to WUS)     -   GUMMEI Globally Unique MME Identifier     -   GUTI Globally Unique Temporary UE Identity     -   HARQ Hybrid ARQ, Hybrid Automatic Repeat Request     -   HANDO, HO Handover     -   HFN HyperFrame Number     -   HHO Hard Handover     -   HLR Home Location Register     -   HN Home Network     -   HO Handover     -   HPLMN Home Public Land Mobile Network     -   HSDPA High Speed Downlink Packet Access     -   HSN Hopping Sequence Number     -   HSPA High Speed Packet Access     -   HSS Home Subscriber Server     -   HSUPA High Speed Uplink Packet Access     -   HTTP Hyper Text Transfer Protocol     -   HTTPS Hyper Text Transfer Protocol Secure (https is http/1.1         over SSL, e.g., port 443)     -   I-Block Information Block     -   ICCID Integrated Circuit Card Identification     -   ICIC Inter-Cell Interference Coordination     -   ID Identity, identifier     -   IDFT Inverse Discrete Fourier Transform     -   IE Information element     -   IBE In-Band Emission     -   IEEE Institute of Electrical and Electronics Engineers     -   IEI Information Element Identifier     -   IEIDL Information Element Identifier Data Length     -   IETF Internet Engineering Task Force     -   IF Infrastructure     -   IM Interference Measurement, Intermodulation, IP Multimedia     -   IMC IMS Credentials     -   IMEI International Mobile Equipment Identity     -   IMGI International mobile group identity     -   IMPI IP Multimedia Private Identity     -   IMPU IP Multimedia PUblic identity     -   IMS IP Multimedia Subsystem     -   IMSI International Mobile Subscriber Identity     -   IoT Internet of Things     -   IP Internet Protocol     -   Ipsec IP Security, Internet Protocol Security     -   IP-CAN IP-Connectivity Access Network     -   IP-M IP Multicast     -   IPv4 Internet Protocol Version 4     -   IPv6 Internet Protocol Version 6     -   IR Infrared     -   IS In Sync     -   IRP Integration Reference Point     -   ISDN Integrated Services Digital Network     -   ISIM IM Services Identity Module     -   ISO International Organisation for Standardisation     -   ISP Internet Service Provider     -   IWF Interworking-Function     -   I-WLAN Interworking WLAN     -   K Constraint length of the convolutional code, USIM Individual         key     -   kB Kilobyte (1000 bytes)     -   kbps kilo-bits per second     -   Kc Ciphering key     -   Ki Individual subscriber authentication key     -   KPI Key Performance Indicator     -   KQI Key Quality Indicator     -   KSI Key Set Identifier     -   ksps kilo-symbols per second     -   KVM Kernel Virtual Machine     -   L1 Layer 1 (physical layer)     -   L1-RSRP Layer 1 reference signal received power     -   L2 Layer 2 (data link layer)     -   L3 Layer 3 (network layer)     -   LAA Licensed Assisted Access     -   LAN Local Area Network     -   LBT Listen Before Talk     -   LCM LifeCycle Management     -   LCR Low Chip Rate     -   LCS Location Services     -   LCID Logical Channel ID     -   LI Layer Indicator     -   LLC Logical Link Control, Low Layer Compatibility     -   LPLMN Local PLMN     -   LPP LTE Positioning Protocol     -   LSB Least Significant Bit     -   LTE Long Term Evolution     -   LWA LTE-WLAN aggregation     -   LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel     -   LTE Long Term Evolution     -   M2M Machine-to-Machine     -   MAC Medium Access Control (protocol layering context)     -   MAC Message authentication code (security/encryption context)     -   MAC-A MAC used for authentication and key agreement (TSG T WG3         context)     -   MAC-I MAC used for data integrity of signalling messages (TSG T         WG3 context)     -   MANO Management and Orchestration

MBMS Multimedia Broadcast and Multicast Service

-   -   MB SFN Multimedia Broadcast multicast service Single Frequency         Network     -   MCC Mobile Country Code     -   MCG Master Cell Group     -   MCOT Maximum Channel Occupancy Time     -   MCS Modulation and coding scheme     -   MDAF Management Data Analytics Function     -   MDAS Management Data Analytics Service     -   MDT Minimization of Drive Tests     -   ME Mobile Equipment     -   MeNB master eNB     -   MER Message Error Ratio     -   MGL Measurement Gap Length     -   MGRP Measurement Gap Repetition Period     -   MIB Master Information Block, Management Information Base     -   MIMO Multiple Input Multiple Output     -   MLC Mobile Location Centre     -   MM Mobility Management     -   MME Mobility Management Entity     -   MN Master Node     -   MO Measurement Object, Mobile Originated     -   MPBCH MTC Physical Broadcast CHannel     -   MPDCCH MTC Physical Downlink Control CHannel     -   MPDSCH MTC Physical Downlink Shared CHannel     -   MPRACH MTC Physical Random Access CHannel     -   MPUSCH MTC Physical Uplink Shared Channel     -   MPLS MultiProtocol Label Switching     -   MS Mobile Station     -   MSB Most Significant Bit     -   MSC Mobile Switching Centre     -   MSI Minimum System Information, MCH Scheduling Information     -   MSID Mobile Station Identifier     -   MSIN Mobile Station Identification Number     -   MSISDN Mobile Subscriber ISDN Number     -   MT Mobile Terminated, Mobile Termination     -   MTC Machine-Type Communications     -   mMTC massive MTC, massive Machine-Type Communications     -   MU-MIMO Multi User MIMO     -   MWUS MTC wake-up signal, MTC WUS     -   NACK Negative Acknowledgement     -   NAI Network Access Identifier     -   NAS Non-Access Stratum, Non-Access Stratum layer     -   NCT Network Connectivity Topology     -   NEC Network Capability Exposure     -   NE-DC NR-E-UTRA Dual Connectivity     -   NEF Network Exposure Function     -   NF Network Function     -   NFP Network Forwarding Path     -   NFPD Network Forwarding Path Descriptor     -   NFV Network Functions Virtualization     -   NFVI NFV Infrastructure     -   NFVO NFV Orchestrator     -   NG Next Generation, Next Gen     -   NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity     -   NM Network Manager     -   NMS Network Management System     -   N-PoP Network Point of Presence     -   NMIB, N-MIB Narrowband MIB     -   NPBCH Narrowband Physical Broadcast CHannel     -   NPDCCH Narrowband Physical Downlink Control CHannel     -   NPDSCH Narrowband Physical Downlink Shared CHannel     -   NPRACH Narrowband Physical Random Access CHannel     -   NPUSCH Narrowband Physical Uplink Shared CHannel     -   NPSS Narrowband Primary Synchronization Signal     -   NSSS Narrowband Secondary Synchronization Signal     -   NR New Radio, Neighbour Relation     -   NRF NF Repository Function     -   NRS Narrowband Reference Signal     -   NS Network Service     -   NSA Non-Standalone operation mode     -   NSD Network Service Descriptor     -   NSR Network Service Record     -   NSSAI Network Slice Selection Assistance Information     -   S-NNSAI Single-NS SAI     -   NSSF Network Slice Selection Function     -   NW Network     -   NWUS Narrowband wake-up signal, Narrowband WUS     -   NZP Non-Zero Power     -   O&M Operation and Maintenance     -   OCB Occupied Channel Bandwidth     -   ODU2 Optical channel Data Unit—type 2     -   OFDM Orthogonal Frequency Division Multiplexing     -   OFDMA Orthogonal Frequency Division Multiple Access     -   OOB Out-of-band     -   OOS Out of Sync     -   OPEX OPerating EXpense     -   OSI Other System Information     -   OSS Operations Support System     -   OTA over-the-air     -   PAPR Peak-to-Average Power Ratio     -   PAR Peak to Average Ratio     -   PBCH Physical Broadcast Channel     -   PC Power Control, Personal Computer     -   PCC Primary Component Carrier, Primary CC     -   PCell Primary Cell     -   PCI Physical Cell ID, Physical Cell Identity     -   PCEF Policy and Charging Enforcement Function     -   PCF Policy Control Function     -   PCRF Policy Control and Charging Rules Function     -   PDCP Packet Data Convergence Protocol, Packet Data Convergence         Protocol layer     -   PDCCH Physical Downlink Control Channel     -   PDCP Packet Data Convergence Protocol     -   PDN Packet Data Network, Public Data Network     -   PDSCH Physical Downlink Shared Channel     -   PDU Protocol Data Unit     -   PEI Permanent Equipment Identifiers     -   PFD Packet Flow Description     -   P-GW PDN Gateway     -   PHICH Physical hybrid-ARQ indicator channel     -   PHY Physical layer     -   PLMN Public Land Mobile Network     -   PIN Personal Identification Number     -   PM Performance Measurement     -   PMI Precoding Matrix Indicator     -   PNF Physical Network Function     -   PNFD Physical Network Function Descriptor     -   PNFR Physical Network Function Record     -   POC PTT over Cellular     -   PP, PTP Point-to-Point     -   PPP Point-to-Point Protocol     -   PRACH Physical RACH     -   PRB Physical resource block     -   PRG Physical resource block group     -   ProSe Proximity Services, Proximity-Based Service     -   PRS Positioning Reference Signal     -   PRR Packet Reception Radio     -   PS Packet Services     -   PSD Power Spectral Density     -   PSBCH Physical Sidelink Broadcast Channel     -   PSDCH Physical Sidelink Downlink Channel     -   PSCCH Physical Sidelink Control Channel     -   PSSCH Physical Sidelink Shared Channel     -   PSCell Primary SCell     -   PSS Primary Synchronization Signal     -   PSTN Public Switched Telephone Network     -   PT-RS Phase-tracking reference signal     -   PTT Push-to-Talk     -   PUCCH Physical Uplink Control Channel     -   PUSCH Physical Uplink Shared Channel     -   QAM Quadrature Amplitude Modulation     -   QCI QoS class of identifier     -   QCL Quasi co-location     -   QFI QoS Flow ID, QoS Flow Identifier     -   QoS Quality of Service     -   QPSK Quadrature (Quaternary) Phase Shift Keying     -   QZSS Quasi-Zenith Satellite System     -   RA-RNTI Random Access RNTI     -   RAB Radio Access Bearer, Random Access Burst     -   RACH Random Access Channel     -   RADIUS Remote Authentication Dial In User Service     -   RAN Radio Access Network     -   RAND RANDom number (used for authentication)     -   RAR Random Access Response     -   RAT Radio Access Technology     -   RAU Routing Area Update     -   RB Resource block, Radio Bearer     -   RBG Resource block group     -   REG Resource Element Group     -   Rel Release     -   REQ REQuest     -   RF Radio Frequency     -   RI Rank Indicator     -   RIV Resource indicator value     -   RL Radio Link     -   RLC Radio Link Control, Radio Link Control layer     -   RLC AM RLC Acknowledged Mode     -   RLC UM RLC Unacknowledged Mode     -   RLF Radio Link Failure     -   RLM Radio Link Monitoring     -   RLM-RS Reference Signal for RLM     -   RM Registration Management     -   RMC Reference Measurement Channel     -   RMSI Remaining MSI, Remaining Minimum System Information     -   RN Relay Node     -   RNC Radio Network Controller     -   RNL Radio Network Layer     -   RNTI Radio Network Temporary Identifier     -   ROHC RObust Header Compression     -   RRC Radio Resource Control, Radio Resource Control layer     -   RRM Radio Resource Management     -   RS Reference Signal     -   RSRP Reference Signal Received Power     -   RSRQ Reference Signal Received Quality     -   RSSI Received Signal Strength Indicator     -   RSU Road Side Unit     -   RSTD Reference Signal Time difference     -   RTP Real Time Protocol     -   RTS Ready-To-Send     -   RTT Round Trip Time     -   Rx Reception, Receiving, Receiver     -   S1AP S1 Application Protocol     -   S1-MME S1 for the control plane     -   S1-U S1 for the user plane     -   S-GW Serving Gateway     -   S-RNTI SRNC Radio Network Temporary Identity     -   S-TMSI SAE Temporary Mobile Station Identifier     -   SA Standalone operation mode     -   SAE System Architecture Evolution     -   SAP Service Access Point     -   SAPD Service Access Point Descriptor     -   SAPI Service Access Point Identifier     -   SCC Secondary Component Carrier, Secondary CC     -   SCell Secondary Cell     -   SC-FDMA Single Carrier Frequency Division Multiple Access     -   SCG Secondary Cell Group     -   SCM Security Context Management     -   SCS Subcarrier Spacing     -   SCTP Stream Control Transmission Protocol     -   SDAP Service Data Adaptation Protocol, Service Data Adaptation         Protocol layer     -   SDL Supplementary Downlink     -   SDNF Structured Data Storage Network Function     -   SDP Session Description Protocol     -   SDSF Structured Data Storage Function     -   SDU Service Data Unit     -   SEAF Security Anchor Function     -   SeNB secondary eNB     -   SEPP Security Edge Protection Proxy     -   SFI Slot format indication     -   SFTD Space-Frequency Time Diversity, SFN and frame timing         difference     -   SFN System Frame Number     -   SgNB Secondary gNB     -   SGSN Serving GPRS Support Node     -   S-GW Serving Gateway     -   SI System Information     -   SI-RNTI System Information RNTI     -   SIB System Information Block     -   SIM Subscriber Identity Module     -   SIP Session Initiated Protocol     -   SiP System in Package     -   SL Sidelink     -   SLA Service Level Agreement     -   SM Session Management     -   SMF Session Management Function     -   SMS Short Message Service     -   SMSF SMS Function     -   SMTC SSB-based Measurement Timing Configuration     -   SN Secondary Node, Sequence Number     -   SoC System on Chip     -   SON Self-Organizing Network     -   SpCell Special Cell     -   SP-CSI-RNTI Semi-Persistent CSI RNTI     -   SPS Semi-Persistent Scheduling     -   SQN Sequence number     -   SR Scheduling Request     -   SRB Signalling Radio Bearer     -   SRS Sounding Reference Signal     -   SS Synchronization Signal     -   SSB Synchronization Signal Block, SS/PBCH Block     -   SSBRI SS/PBCH Block Resource Indicator, Synchronization Signal         Block Resource Indicator     -   SSC Session and Service Continuity     -   SS-RSRP Synchronization Signal based Reference Signal Received         Power     -   SS-RSRQ Synchronization Signal based Reference Signal Received         Quality     -   SS-SINR Synchronization Signal based Signal to Noise and         Interference Ratio     -   SSS Secondary Synchronization Signal     -   SSSG Search Space Set Group     -   SSSIF Search Space Set Indicator     -   SST Slice/Service Types     -   SU-MIMO Single User MIMO     -   SUL Supplementary Uplink     -   TA Timing Advance, Tracking Area     -   TAC Tracking Area Code     -   TAG Timing Advance Group     -   TAU Tracking Area Update     -   TB Transport Block     -   TBS Transport Block Size     -   TBD To Be Defined     -   TCI Transmission Configuration Indicator     -   TCP Transmission Communication Protocol     -   TDD Time Division Duplex     -   TDM Time Division Multiplexing     -   TDMA Time Division Multiple Access     -   TE Terminal Equipment     -   TEID Tunnel End Point Identifier     -   TFT Traffic Flow Template     -   TMSI Temporary Mobile Subscriber Identity     -   TNL Transport Network Layer     -   TPC Transmit Power Control     -   TPMI Transmitted Precoding Matrix Indicator     -   TR Technical Report     -   TRP, TRxP Transmission Reception Point     -   TRS Tracking Reference Signal     -   TRx Transceiver     -   TS Technical Specifications, Technical Standard     -   TTI Transmission Time Interval     -   Tx Transmission, Transmitting, Transmitter     -   U-RNTI UTRAN Radio Network Temporary Identity     -   UART Universal Asynchronous Receiver and Transmitter     -   UCI Uplink Control Information     -   UE User Equipment     -   UDM Unified Data Management     -   UDP User Datagram Protocol     -   UDSF Unstructured Data Storage Network Function     -   UICC Universal Integrated Circuit Card     -   UL Uplink     -   UM Unacknowledged Mode     -   UML Unified Modelling Language     -   UMTS Universal Mobile Telecommunications System     -   UP User Plane     -   UPF User Plane Function     -   URI Uniform Resource Identifier     -   URL Uniform Resource Locator     -   URLLC Ultra-Reliable and Low Latency     -   USB Universal Serial Bus     -   USIM Universal Subscriber Identity Module     -   USS UE-specific search space     -   UTRA UMTS Terrestrial Radio Access     -   UTRAN Universal Terrestrial Radio Access Network     -   UwPTS Uplink Pilot Time Slot     -   V2I Vehicle-to-Infrastruction     -   V2P Vehicle-to-Pedestrian     -   V2V Vehicle-to-Vehicle     -   V2X Vehicle-to-everything     -   VIM Virtualized Infrastructure Manager     -   VL Virtual Link,     -   VLAN Virtual LAN, Virtual Local Area Network     -   VM Virtual Machine     -   VNF Virtualized Network Function     -   VNFFG VNF Forwarding Graph     -   VNFFGD VNF Forwarding Graph Descriptor     -   VNFM VNF Manager     -   VoIP Voice-over-IP, Voice-over-Internet Protocol     -   VPLMN Visited Public Land Mobile Network     -   VPN Virtual Private Network     -   VRB Virtual Resource Block     -   WiMAX Worldwide Interoperability for Microwave Access     -   WLAN Wireless Local Area Network     -   WMAN Wireless Metropolitan Area Network     -   WPAN Wireless Personal Area Network     -   X2-C X2-Control plane     -   X2-U X2-User plane     -   XML eXtensible Markup Language     -   XRES EXpected user RESponse     -   XOR eXclusive OR     -   ZC Zadoff-Chu     -   ZP Zero Power

Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein, but are not meant to be limiting.

The term “circuitry” refers to a circuit or system of multiple circuits configured to perform a particular function in an electronic device. The circuit or system of circuits may be part of, or include one or more hardware components, such as a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable gate array (FPGA), programmable logic device (PLD), complex PLD (CPLD), high-capacity PLD (HCPLD), System-on-Chip (SoC), System-in-Package (SiP), Multi-Chip Package (MCP), digital signal processor (DSP), etc., that are configured to provide the described functionality. In addition, the term “circuitry” may also refer to a combination of one or more hardware elements with the program code used to carry out the functionality of that program code. Some types of circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. Such a combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “memory” and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including random access memory (RAM), magnetoresistive RAM (MRAM), phase change random access memory (PRAM), dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), core memory, read only memory (ROM), magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data. The term “computer-readable medium” may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “element” refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.

The term “device” refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity.

The term “entity” refers to a distinct component of an architecture or device, or information transferred as a payload.

The term “controller” refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “admission control” refers to a validation process in communication systems where a check is performed before a connection is established to see if current resources are sufficient for the proposed connection.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell. 

1. A method of operating a user equipment (UE) comprising: generating, by the UE, an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace; and transmitting, by the UE, the uplink signal over a PUCCH that utilizes unlicensed spectrum in a wireless network.
 2. The method of claim 1, further comprising: determining, by the UE, a value of “n” based on an uplink control information (UCI) payload size; and choosing, by the UE, a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.
 3. The method of claim 1, further comprising receiving, by the UE, one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.
 4. The method of claim 3, wherein the generating further comprises determining, by the UE, a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.
 5. The method of claim 4, further comprising configuring, by the UE, a starting interlace and a number of interlaces as a PUCCH resource allocation for PUCCH format 2 in a frequency domain.
 6. The method of claim 1, wherein the generating further comprises determining, by the UE, a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).
 7. The method of claim 6, wherein Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.
 8. A non-transitory computer readable medium having instructions stored thereon that, when executed by a user equipment (UE), cause the UE to perform operations comprising: generating an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain of a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace; and transmitting the uplink signal over a PUCCH that utilizes unlicensed spectrum in a wireless network.
 9. The non-transitory computer readable medium of claim 8, wherein the operations further comprise: determining a value of “n” based on an uplink control information (UCI) payload size; and choosing a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.
 10. The non-transitory computer readable medium of claim 8, wherein the operations further comprise receiving one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.
 11. The non-transitory computer readable medium of claim 10, wherein the generating further comprises determining a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.
 12. The non-transitory computer readable medium of claim 11, wherein the generating further comprises configuring a starting interlace and a number of interlaces as a PUCCH resource allocation for PUCCH format 2 in a frequency domain.
 13. The non-transitory computer readable medium of claim 8, wherein the generating further comprises determining a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).
 14. The non-transitory computer readable medium of claim 13, wherein Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1.
 15. A user equipment (UE) comprising: processor circuitry configured to generate an uplink signal according to a physical uplink control channel (PUCCH) format 2 and having “n” number of physical resource blocks (PRBs) that are mapped in an interlaced manner across a frequency domain on a orthogonal frequency division multiplexing (OFDM) symbol, wherein “n” is an integer multiple of a number of PRBs per interlace; and radio front end circuitry, coupled to the processor circuitry, configured to transmit the uplink signal on a PUCCH that utilizes unlicensed spectrum of a wireless network.
 16. The UE of claim 15, wherein the processor circuitry is further configured to: determine a value of “n” based on an uplink control information (UCI) payload size; and choose a code rate less than a configured maximum code rate in order to determine the value of “n” that is divisible by number of PRBs per interlace.
 17. The UE of claim 15, wherein the processor circuitry is further configured to receive one or more frequency domain resources, wherein the frequency domain resources include interlace indices with an index number that is pre-defined in a specification in terms of a starting PRB, an inter-PRB separation, and a number-of-PRBs per interlace.
 18. The UE of claim 17, wherein the processor circuitry is further configured to determine a bitmap used to indicate which interlace to use, and wherein an index of a first interlace to be used is indicated by the bitmap or by k bits, wherein k=┌log₂(x_(int) ^(max))┐ and x_(int) ^(max) is a maximum number of interlaces.
 19. The UE of claim 15, wherein the processor circuitry is further configured to determine a value of “n” based on n=x_(int)*y_(PRB) ^(int)+Δ_(PRB), wherein x_(int) is a number of interlaces assigned to PUSSCH format 2 transmission and y_(PRB) ^(int) is the number of PRBs per interlace and Δ_(PRB) is an excess number of PRBs, and wherein Δ_(PRB)<y_(PRB) ^(int).
 20. The UE of claim 19, wherein Δ_(PRB) is restricted to be a factor of y_(PRB) ^(int) and Δ_(PRB)>1. 